mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-09-08 18:39:20 +02:00
4c310eca2e
unreserved according to the grammar. The list of unreserved words has gotten extensive enough that the unnecessary quoting is becoming a bit of an eyesore. To do this, add knowledge of the keyword category to keywords.c's table. (Someday we might be able to generate keywords.c's table and the keyword lists in gram.y from a common source.) For the moment, lie about WITH's status in the table so it will still get quoted --- this is because of the expectation that WITH will become reserved when the SQL recursive-queries patch gets done. I didn't force initdb because this affects nothing on-disk; but note that a few regression tests have changed expected output. |
||
---|---|---|
.. | ||
po | ||
common.c | ||
dumputils.c | ||
dumputils.h | ||
Makefile | ||
nls.mk | ||
pg_backup_archiver.c | ||
pg_backup_archiver.h | ||
pg_backup_custom.c | ||
pg_backup_db.c | ||
pg_backup_db.h | ||
pg_backup_files.c | ||
pg_backup_null.c | ||
pg_backup_tar.c | ||
pg_backup_tar.h | ||
pg_backup.h | ||
pg_dump_sort.c | ||
pg_dump.c | ||
pg_dump.h | ||
pg_dumpall.c | ||
pg_restore.c | ||
README |
Notes on pg_dump ================ 1. pg_dump, by default, still outputs text files. 2. pg_dumpall forces all pg_dump output to be text, since it also outputs text into the same output stream. 3. The plain text output format cannot be used as input into pg_restore. To dump a database into the new custom format, type: pg_dump <db-name> -Fc > <backup-file> or, to dump in TAR format pg_dump <db-name> -Ft > <backup-file> To restore, try To list contents: pg_restore -l <backup-file> | less or to list tables: pg_restore <backup-file> --table | less or to list in a different order pg_restore <backup-file> -l --oid --rearrange | less Once you are happy with the list, just remove the '-l', and an SQL script will be output. You can also dump a listing: pg_restore -l <backup-file> > toc.lis or pg_restore -l <backup-file> -f toc.lis edit it, and rearrange the lines (or delete some): vi toc.lis then use it to restore selected items: pg_restore <backup-file> --use=toc.lis -l | less When you like the list, type pg_restore backup.bck --use=toc.lis > script.sql or, simply: createdb newdbname pg_restore backup.bck --use=toc.lis | psql newdbname TAR === The TAR archive that pg_dump creates currently has a blank username & group for the files, but should be otherwise valid. It also includes a 'restore.sql' script which is there for the benefit of humans. The script is never used by pg_restore. Note: the TAR format archive can only be used as input into pg_restore if it is in TAR form. (ie. you should not extract the files then expect pg_restore to work). You can extract, edit, and tar the files again, and it should work, but the 'toc' file should go at the start, the data files be in the order they are used, and the BLOB files at the end. Philip Warner, 16-Jul-2000 pjw@rhyme.com.au