From 8bfe93c5c8b10c9a824fd07138c55d3a857f4e98 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Wed, 11 Jun 2003 16:29:42 +0000 Subject: pg_dump and pg_restore were stripping quotes and downcasing some but not all SQL identifiers taken from command line arguments. We decided years ago that that was a bad idea: identifiers taken from the command line should be treated as literally correct. Remove the inconsistent code that has crept in recently. Also fix pg_dump so that the combination of --schema and --table does what you'd expect, namely dump exactly one table from exactly one schema. Per gripe from Deepak Bhole of Red Hat. --- doc/src/sgml/ref/pg_dump.sgml | 22 +++++++++++----------- doc/src/sgml/ref/pg_restore.sgml | 10 ++++++---- 2 files changed, 17 insertions(+), 15 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml index 79f30c771f9..5b9e2d4c40e 100644 --- a/doc/src/sgml/ref/pg_dump.sgml +++ b/doc/src/sgml/ref/pg_dump.sgml @@ -1,5 +1,5 @@ @@ -287,9 +287,9 @@ PostgreSQL documentation In this mode, pg_dump makes no - attempt to dump any other database objects that may depend - upon objects in the selected schema. Therefore, there is no - guarantee that the results of a single schema dump can be + attempt to dump any other database objects that objects in the + selected schema may depend upon. Therefore, there is no + guarantee that the results of a single-schema dump can be successfully restored by themselves into a clean database. @@ -394,18 +394,18 @@ PostgreSQL documentation Dump data for table - only. If * is specified, all tables in the - specified database will be dumped. It is possible for there to be + only. It is possible for there to be multiple tables with the same name in different schemas; if that - is the case, all matching tables will be dumped. + is the case, all matching tables will be dumped. Specify both + In this mode, pg_dump makes no - attempt to dump any other database objects that may depend - upon the selected table. Therefore, there is no guarantee - that the results of a single table dump can be successfully + attempt to dump any other database objects that the selected table + may depend upon. Therefore, there is no guarantee + that the results of a single-table dump can be successfully restored by themselves into a clean database. @@ -652,7 +652,7 @@ CREATE DATABASE foo WITH TEMPLATE template0; Once restored, it is wise to run ANALYZE on each - restored object so the optimizer has useful statistics. + restored table so the optimizer has useful statistics. diff --git a/doc/src/sgml/ref/pg_restore.sgml b/doc/src/sgml/ref/pg_restore.sgml index ffc019b3e55..cf028b93e59 100644 --- a/doc/src/sgml/ref/pg_restore.sgml +++ b/doc/src/sgml/ref/pg_restore.sgml @@ -1,4 +1,4 @@ - + @@ -269,7 +269,9 @@ - Restore the named function only. + Restore the named function only. Be careful to spell the function + name and arguments exactly as they appear in the dump file's table + of contents. @@ -318,7 +320,7 @@ - Restore only the schema (data defintions), not the data. + Restore only the schema (data definitions), not the data. Sequence values will be reset. @@ -557,7 +559,7 @@ CREATE DATABASE foo WITH TEMPLATE template0; Once restored, it is wise to run ANALYZE on each - restored object so the optimizer has useful statistics. + restored table so the optimizer has useful statistics. -- cgit v1.2.3