diff options
| author | Bruce Momjian <bruce@momjian.us> | 2004-07-13 03:00:17 +0000 |
|---|---|---|
| committer | Bruce Momjian <bruce@momjian.us> | 2004-07-13 03:00:17 +0000 |
| commit | dc0e76ca36b4f7b91c3b83e53012585c5eccbe98 (patch) | |
| tree | b4f83c3908358ae84eacdcce38786812bfcffef7 /doc/src | |
| parent | e419c84c56a70d62ec267084ecf814bf132d0528 (diff) | |
| download | postgresql-dc0e76ca36b4f7b91c3b83e53012585c5eccbe98.tar.gz postgresql-dc0e76ca36b4f7b91c3b83e53012585c5eccbe98.zip | |
Change pg_dump to use ALTER OWNER commands instead of SET SESSION
AUTHORIZATION commands by default. Move all GRANT and REVOKE commands
to the end of the dump to avoid restore failures in several situations.
Bring back --use-set-session-authorization option to get previous SET
behaviour
Christopher Kings-Lyne
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/ref/pg_dump.sgml | 10 | ||||
| -rw-r--r-- | doc/src/sgml/ref/pg_restore.sgml | 10 |
2 files changed, 10 insertions, 10 deletions
diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml index b3dd617136b..72ec981fcc5 100644 --- a/doc/src/sgml/ref/pg_dump.sgml +++ b/doc/src/sgml/ref/pg_dump.sgml @@ -1,5 +1,5 @@ <!-- -$PostgreSQL: pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.72 2004/07/10 15:51:28 momjian Exp $ +$PostgreSQL: pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.73 2004/07/13 02:59:49 momjian Exp $ PostgreSQL documentation --> @@ -464,10 +464,10 @@ PostgreSQL documentation <term><option>--use-set-session-authorization</></term> <listitem> <para> - This option is obsolete but still accepted for backwards - compatibility. - <application>pg_dump</application> now always behaves in the - way formerly selected by this option. + Output SQL standard SET SESSION AUTHORIZATION commands instead + of OWNER TO commands. This makes the dump more standards compatible, + but depending on the history of the objects in the dump, may not + restore properly. </para> </listitem> </varlistentry> diff --git a/doc/src/sgml/ref/pg_restore.sgml b/doc/src/sgml/ref/pg_restore.sgml index 8f4c1cd9b92..533bdd9c0b8 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.46 2004/02/17 09:07:16 neilc Exp $ --> +<!-- $PostgreSQL: pgsql/doc/src/sgml/ref/pg_restore.sgml,v 1.47 2004/07/13 02:59:49 momjian Exp $ --> <refentry id="APP-PGRESTORE"> <refmeta> @@ -337,10 +337,10 @@ <term><option>--use-set-session-authorization</option></term> <listitem> <para> - This option is obsolete but still accepted for backwards - compatibility. - <application>pg_restore</application> now always behaves in the - way formerly selected by this option. + Output SQL standard SET SESSION AUTHORIZATION commands instead + of OWNER TO commands. This makes the dump more standards compatible, + but depending on the history of the objects in the dump, may not + restore properly. </para> </listitem> </varlistentry> |