rdelaage
/
postgresql
mirror of https://git.postgresql.org/git/postgresql.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
postgresql/src/bin/pg_dump
History
Tom Lane 7bddca3450 Fix up foreign-key mechanism so that there is a sound semantic basis for the 
equality checks it applies, instead of a random dependence on whatever
operators might be named "=".  The equality operators will now be selected
from the opfamily of the unique index that the FK constraint depends on to
enforce uniqueness of the referenced columns; therefore they are certain to be
consistent with that index's notion of equality.  Among other things this
should fix the problem noted awhile back that pg_dump may fail for foreign-key
constraints on user-defined types when the required operators aren't in the
search path.  This also means that the former warning condition about "foreign
key constraint will require costly sequential scans" is gone: if the
comparison condition isn't indexable then we'll reject the constraint
entirely. All per past discussions.

Along the way, make the RI triggers look into pg_constraint for their
information, instead of using pg_trigger.tgargs; and get rid of the always
error-prone fixed-size string buffers in ri_triggers.c in favor of building up
the RI queries in StringInfo buffers.

initdb forced due to columns added to pg_constraint and pg_trigger.
 		2007-02-14 01:58:58 +00:00
..
po Translation updates 2006-12-02 01:16:16 +00:00
Makefile Update CVS HEAD for 2007 copyright. Back branches are typically not 2007-01-05 22:20:05 +00:00
README pg_dump can now dump large objects even in plain-text output mode, by 2005-06-21 20:45:44 +00:00
common.c Update pg_dump to support dumping operator families. 2007-01-23 17:54:50 +00:00
dumputils.c Update CVS HEAD for 2007 copyright. Back branches are typically not 2007-01-05 22:20:05 +00:00
dumputils.h Update CVS HEAD for 2007 copyright. Back branches are typically not 2007-01-05 22:20:05 +00:00
nls.mk Add missing "ko". 2005-01-25 17:32:00 +00:00
pg_backup.h Add 'output file' option for pg_dumpall, especially useful for Win32, 2007-01-25 03:30:43 +00:00
pg_backup_archiver.c Wording cleanup for error messages. Also change can't -> cannot. 2007-02-01 19:10:30 +00:00
pg_backup_archiver.h Add 'output file' option for pg_dumpall, especially useful for Win32, 2007-01-25 03:30:43 +00:00
pg_backup_custom.c pgindent run for 8.2. 2006-10-04 00:30:14 +00:00
pg_backup_db.c pgindent run for 8.2. 2006-10-04 00:30:14 +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 Normalize fgets() calls to use sizeof() for calculating the buffer size 2007-02-08 11:10:27 +00:00
pg_backup_null.c Remove 576 references of include files that were not needed. 2006-07-14 14:52:27 +00:00
pg_backup_tar.c pg_restore failed on tar-format archives if they contained large objects 2006-11-01 15:59:26 +00:00
pg_backup_tar.h $Header: -> $PostgreSQL Changes ... 2003-11-29 19:52:15 +00:00
pg_dump.c Fix up foreign-key mechanism so that there is a sound semantic basis for the 2007-02-14 01:58:58 +00:00
pg_dump.h Update pg_dump to support dumping operator families. 2007-01-23 17:54:50 +00:00
pg_dump_sort.c Update pg_dump to support dumping operator families. 2007-01-23 17:54:50 +00:00
pg_dumpall.c StrNCpy -> strlcpy (not complete) 2007-02-10 14:58:55 +00:00
pg_restore.c Code review for --no-data-for-failed-tables patch. Instead of trashing 2006-10-14 23:07:22 +00:00
win32.mak Fix pg_dump linking on Win32 with MSVS win32.mak: 2006-12-04 22:26:17 +00:00

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