postgresql/src/bin/pg_dump
Bruce Momjian b492c3accc Add parentheses to macros when args are used in computations. Without
them, the executation behavior could be unexpected.
2005-05-25 21:40:43 +00:00
..
po Translation updates 2005-01-17 21:21:18 +00:00
common.c Tag appropriate files for rc3 2004-12-31 22:04:05 +00:00
dumputils.c GCC 4.0 includes a new warning option, -Wformat-literal, that emits 2005-04-30 08:08:51 +00:00
dumputils.h Tag appropriate files for rc3 2004-12-31 22:04:05 +00:00
Makefile Have libpgport link before libpq so that PG client applications are more 2005-03-25 18:17:14 +00:00
nls.mk Add missing "ko". 2005-01-25 17:32:00 +00:00
pg_backup_archiver.c Guard against duplicate IDs in input file in SortTocFromFile(). 2005-05-17 17:30:29 +00:00
pg_backup_archiver.h Add parentheses to macros when args are used in computations. Without 2005-05-25 21:40:43 +00:00
pg_backup_custom.c Fix breakage created by addition of separate 'acl pass' in pg_dump. 2005-01-25 22:44:31 +00:00
pg_backup_db.c Update pg_dump to use SET DEFAULT_TABLESPACE instead of explicit 2004-11-06 19:36:02 +00:00
pg_backup_db.h Modify pg_dump so that the preferred dump order is by name within 2004-03-03 21:28:55 +00:00
pg_backup_files.c Modify pg_dump so that the preferred dump order is by name within 2004-03-03 21:28:55 +00:00
pg_backup_null.c Work around naming conflict between zlib and OpenSSL by tweaking inclusion 2003-12-08 16:39:05 +00:00
pg_backup_tar.c Fix breakage created by addition of separate 'acl pass' in pg_dump. 2005-01-25 22:44:31 +00:00
pg_backup_tar.h $Header: -> $PostgreSQL Changes ... 2003-11-29 19:52:15 +00:00
pg_backup.h Update pg_dump to use SET DEFAULT_TABLESPACE instead of explicit 2004-11-06 19:36:02 +00:00
pg_dump_sort.c Fix minor thinko in logic to set dump order when dumping from a pre-7.3 2005-02-03 23:38:58 +00:00
pg_dump.c GCC 4.0 includes a new warning option, -Wformat-literal, that emits 2005-04-30 08:08:51 +00:00
pg_dump.h Tag appropriate files for rc3 2004-12-31 22:04:05 +00:00
pg_dumpall.c pg_dumpall should enforce the server version check for itself, rather 2005-04-18 23:47:52 +00:00
pg_restore.c This patch fixes a bug in the error message emitted by pg_restore on an 2005-04-29 07:08:06 +00:00
README - Support for BLOB output from pg_dump and input via pg_restore 2000-07-21 11:40:08 +00:00

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 can not be used as input into pg_restore.

4. pg_dump now dumps the items in a modified OID order to try to improve relaibility of default restores.


To dump a database into the next custom format, type:

    pg_dump <db-name> -Fc > <backup-file>

or, 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 differnet orderL

       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


BLOBs
=====

To dump blobs you must use the custom archive format (-Fc) or TAR format (-Ft), and specify the 
--blobs qualifier to the pg_dump command.

To restore blobs you must use a direct database connection (--db=db-to-restore-to).

eg.

   pg_dump --blob -Fc db-to-backup -f backup.bck

   pg_restore backup.bck --db=db-to-restore-into


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. It 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