postgresql/src/bin/pg_dump
Tom Lane b2734a0d79 Support SQL-compliant triggers on columns, ie fire only if certain columns
are named in the UPDATE's SET list.

Note: the schema of pg_trigger has not actually changed; we've just started
to use a column that was there all along.  catversion bumped anyway so that
this commit is included in the history of potentially interesting changes
to system catalog contents.

Itagaki Takahiro
2009-10-14 22:14:25 +00:00
..
po Translation updates for 8.4 release. 2009-06-26 19:33:52 +00:00
Makefile Update of install-sh, mkinstalldirs, and associated configury 2009-08-26 22:24:44 +00:00
README More README src cleanups. 2008-03-21 13:23:29 +00:00
common.c Create an ALTER DEFAULT PRIVILEGES command, which allows users to adjust 2009-10-05 19:24:49 +00:00
dumputils.c Use plurals (TABLES, FUNCTIONS, etc) in ALTER DEFAULT PRIVILEGES. We have 2009-10-12 23:41:45 +00:00
dumputils.h Make it possibly to specify GUC params per user and per database. 2009-10-07 22:14:26 +00:00
keywords.c Tweak the core scanner so that it can be used by plpgsql too. 2009-07-14 20:24:10 +00:00
nls.mk Translation updates for 8.4 release. 2009-06-26 19:33:52 +00:00
pg_backup.h 8.4 pgindent run, with new combined Linux/FreeBSD/MinGW typedef list 2009-06-11 14:49:15 +00:00
pg_backup_archiver.c Create an ALTER DEFAULT PRIVILEGES command, which allows users to adjust 2009-10-05 19:24:49 +00:00
pg_backup_archiver.h Modify parallel pg_restore to track pending and ready items by means of 2009-08-07 22:48:34 +00:00
pg_backup_custom.c Remove unused variable. 2009-08-24 14:15:09 +00:00
pg_backup_db.c 8.4 pgindent run, with new combined Linux/FreeBSD/MinGW typedef list 2009-06-11 14:49:15 +00:00
pg_backup_db.h Mark a few functions as static or NOT_USED. 2006-07-18 17:42:01 +00:00
pg_backup_files.c Make pg_dump/pg_restore --clean options drop large objects too. 2009-07-21 21:46:10 +00:00
pg_backup_null.c Fix pg_dump to do the right thing when escaping the contents of large objects. 2009-08-04 21:56:09 +00:00
pg_backup_tar.c Make pg_dump/pg_restore --clean options drop large objects too. 2009-07-21 21:46:10 +00:00
pg_backup_tar.h $Header: -> $PostgreSQL Changes ... 2003-11-29 19:52:15 +00:00
pg_dump.c Support SQL-compliant triggers on columns, ie fire only if certain columns 2009-10-14 22:14:25 +00:00
pg_dump.h Use pg_get_triggerdef in pg_dump 2009-10-09 21:02:56 +00:00
pg_dump_sort.c Create an ALTER DEFAULT PRIVILEGES command, which allows users to adjust 2009-10-05 19:24:49 +00:00
pg_dumpall.c Make it possibly to specify GUC params per user and per database. 2009-10-07 22:14:26 +00:00
pg_restore.c 8.4 pgindent run, with new combined Linux/FreeBSD/MinGW typedef list 2009-06-11 14:49:15 +00:00

README

$PostgreSQL: pgsql/src/bin/pg_dump/README,v 1.7 2008/03/21 13:23:28 momjian Exp $

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