|
1 | | -<!-- $PostgreSQL: pgsql/doc/src/sgml/ref/pg_restore.sgml,v 1.54 2005/07/25 22:12:31 tgl Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/ref/pg_restore.sgml,v 1.55 2005/07/27 13:42:01 neilc Exp $ --> |
2 | 2 |
|
3 | 3 | <refentry id="APP-PGRESTORE"> |
4 | 4 | <refmeta> |
|
361 | 361 | <term><option>--use-set-session-authorization</option></term> |
362 | 362 | <listitem> |
363 | 363 | <para> |
364 | | - Output SQL standard SET SESSION AUTHORIZATION commands instead of |
365 | | - ALTER OWNER commands. This makes the dump more standards compatible, |
366 | | -but depending onthehistory of the objects in the dump, may not |
367 | | - restore properly. |
| 364 | + Output SQL standard<command>SET SESSION AUTHORIZATION</> |
| 365 | +commands instead of <command>ALTER OWNER</> commands. This |
| 366 | +makesthedump more standards compatible, but depending on the |
| 367 | +history of the objects in the dump, may notrestore properly. |
368 | 368 | </para> |
369 | 369 | </listitem> |
370 | 370 | </varlistentry> |
|
