diff options
Diffstat (limited to 'doc/src/sgml/ref/pg_restore.sgml')
| -rw-r--r-- | doc/src/sgml/ref/pg_restore.sgml | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/doc/src/sgml/ref/pg_restore.sgml b/doc/src/sgml/ref/pg_restore.sgml index a5a939443d9..66d09f42090 100644 --- a/doc/src/sgml/ref/pg_restore.sgml +++ b/doc/src/sgml/ref/pg_restore.sgml @@ -520,25 +520,25 @@ </varlistentry> <varlistentry> - <term><option>--enable-row-security</></term> <listitem> + <term><option>--enable-row-security</></term> + <listitem> <para> This option is relevant only when restoring the contents of a table - which has row security. By default, pg_restore will set - <literal>ROW_SECURITY</literal> to <literal>OFF</literal>, to ensure + which has row security. By default, <application>pg_restore</application> will set + <xref linkend="guc-row-security"> to off, to ensure that all data is restored in to the table. If the user does not have sufficient privileges to bypass row security, then an error is thrown. This parameter instructs <application>pg_restore</application> to set - row_security to 'ON' instead, allowing the user to attempt to restore - the contents of the table with row security enabled. This may still + <xref linkend="guc-row-security"> to on instead, allowing the user to attempt to restore + the contents of the table with row security enabled. This might still fail if the user does not have the right to insert the rows from the dump into the table. </para> <para> - Note that this option currently also requires the dump be in INSERT - format as COPY TO does not support row security. + Note that this option currently also requires the dump be in <command>INSERT</command> + format, as <command>COPY TO</command> does not support row security. </para> - </listitem> </varlistentry> |