postgresql/src/bin/pg_dump
Bruce Momjian 9ae6905520 This is a totally trivial patch for something that was a very minor nit that
annoyed me the other day while I was documenting my current project. It
makes pg_dump use the same layout for types as for tables, by putting "\n\t"
before the first field and "\n" before the final ");"

Can't really justify this too much except to say I had an itch and I
scratched it ;-)

Andrew Dunstan
2003-07-27 03:47:22 +00:00
..
po Czech translation updates from Karel Zak 2003-07-23 09:36:43 +00:00
common.c Apply message style guide to frontend programs. 2003-07-23 08:47:41 +00:00
dumputils.c Fix grant option dumping and related cross-version compatibility issues. 2003-07-24 15:52:53 +00:00
dumputils.h Cause pg_dumpall to include GRANT/REVOKE for database-level permissions 2003-05-30 22:55:16 +00:00
Makefile Don't force rebuild of all of backend/parser when we only need 2002-12-12 21:02:00 +00:00
nls.mk Merge PO file updates from 7.3 branch. 2003-06-28 22:31:01 +00:00
pg_backup.h pgindent run. 2002-09-04 20:31:48 +00:00
pg_backup_archiver.c Apply message style guide to frontend programs. 2003-07-23 08:47:41 +00:00
pg_backup_archiver.h Changes of 6-Sep-02 broke pg_restore's ability to recognize tar-format 2003-02-01 19:29:16 +00:00
pg_backup_custom.c Apply message style guide to frontend programs. 2003-07-23 08:47:41 +00:00
pg_backup_db.c Apply message style guide to frontend programs. 2003-07-23 08:47:41 +00:00
pg_backup_db.h Enable large file support. 2002-08-20 17:54:45 +00:00
pg_backup_files.c Allow fseeko in pg_dump only if fseeko() will work for all supported file 2002-10-25 01:33:17 +00:00
pg_backup_null.c pgindent run. 2002-09-04 20:31:48 +00:00
pg_backup_tar.c Apply message style guide to frontend programs. 2003-07-23 08:47:41 +00:00
pg_backup_tar.h backend where a statically sized buffer is written to. Most of these 2002-08-28 20:46:24 +00:00
pg_dump.c This is a totally trivial patch for something that was a very minor nit that 2003-07-27 03:47:22 +00:00
pg_dump.h It has been tested only against CVS backend, however. Some checking of the 2003-03-20 06:26:30 +00:00
pg_dumpall.c Apply message style guide to frontend programs. 2003-07-23 08:47:41 +00:00
pg_restore.c Apply message style guide to frontend programs. 2003-07-23 08:47:41 +00:00
README - Support for BLOB output from pg_dump and input via pg_restore 2000-07-21 11:40:08 +00:00
sprompt.c Fix off-by-one error in the maxlen parameter handling. 2003-03-18 22:09:37 +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