diff options
author | Tom Lane | 2006-10-14 23:07:22 +0000 |
---|---|---|
committer | Tom Lane | 2006-10-14 23:07:22 +0000 |
commit | 1314983fd302bf53dbf5284145205dea44cb832c (patch) | |
tree | e6e9d5e9e50966e4631f72e929710ba77b6da3e8 /doc | |
parent | f58eac82eeb62635ea870b62654836fb4c331e91 (diff) |
Code review for --no-data-for-failed-tables patch. Instead of trashing
one of the program's core data structures, make use of the existing
ability to selectively exclude TOC items by ID. Slightly more code but
much less likely to create future maintenance problems.
Diffstat (limited to 'doc')
-rw-r--r-- | doc/src/sgml/ref/pg_restore.sgml | 24 |
1 files changed, 16 insertions, 8 deletions
diff --git a/doc/src/sgml/ref/pg_restore.sgml b/doc/src/sgml/ref/pg_restore.sgml index 48552822373..edbbba808f5 100644 --- a/doc/src/sgml/ref/pg_restore.sgml +++ b/doc/src/sgml/ref/pg_restore.sgml @@ -1,4 +1,4 @@ -<!-- $PostgreSQL: pgsql/doc/src/sgml/ref/pg_restore.sgml,v 1.62 2006/10/07 20:59:04 petere Exp $ --> +<!-- $PostgreSQL: pgsql/doc/src/sgml/ref/pg_restore.sgml,v 1.63 2006/10/14 23:07:22 tgl Exp $ --> <refentry id="APP-PGRESTORE"> <refmeta> @@ -396,15 +396,23 @@ </varlistentry> <varlistentry> - <term><option>--no-data-for-failed-tables</></term> + <term><option>--no-data-for-failed-tables</option></term> <listitem> <para> - By default, table data objects are restored even if the - associated table could not be successfully created (e. g. - because it already exists). With this option, such table - data is silently ignored. This is useful for dumping and - restoring databases with tables which contain auxiliary data - for PostgreSQL extensions (e. g. PostGIS). + By default, table data is restored even if the creation command + for the table failed (e.g., because it already exists). + With this option, data for such a table is skipped. + This behavior is useful when the target database may already + contain the desired table contents. For example, + auxiliary tables for <productname>PostgreSQL</> extensions + such as <productname>PostGIS</> may already be loaded in + the target database; specifying this option prevents duplicate + or obsolete data from being loaded into them. + </para> + + <para> + This option is effective only when restoring directly into a + database, not when producing SQL script output. </para> </listitem> </varlistentry> |