168
<term><option>--lock-wait-timeout=<replaceable class="parameter">timeout</replaceable></option></term>
171
Do not wait forever to acquire shared table locks at the beginning of
172
the dump. Instead, fail if unable to lock a table within the specified
173
<replaceable class="parameter">timeout</>. The timeout may be
174
specified in any of the formats accepted by <command>SET
175
statement_timeout</>. Allowed values vary depending on the server
176
version you are dumping from, but an integer number of milliseconds
177
is accepted by all versions since 7.3. This option is ignored when
178
dumping from a pre-7.3 server.
184
<term><option>--no-tablespaces</option></term>
187
Do not output commands to create tablespaces nor select tablespaces
189
With this option, all objects will be created in whichever
190
tablespace is the default during restore.
196
<term><option>--no-security-label</option></term>
199
Do not dump security labels.
205
<term><option>--no-unlogged-table-data</option></term>
208
Do not dump the contents of unlogged tables. This option has no
209
effect on whether or not the table definitions (schema) are dumped;
210
it only suppresses dumping the table data.
216
168
<term><option>-r</option></term>
217
169
<term><option>--roles-only</option></term>
305
<term><option>--inserts</option></term>
308
Dump data as <command>INSERT</command> commands (rather
309
than <command>COPY</command>). This will make restoration very slow;
310
it is mainly useful for making dumps that can be loaded into
311
non-<productname>PostgreSQL</productname> databases. Note that
312
the restore might fail altogether if you have rearranged column order.
313
The <option>--column-inserts</option> option is safer, though even
320
257
<term><option>--column-inserts</option></term>
321
258
<term><option>--attribute-inserts</option></term>
304
<term><option>--inserts</option></term>
307
Dump data as <command>INSERT</command> commands (rather
308
than <command>COPY</command>). This will make restoration very slow;
309
it is mainly useful for making dumps that can be loaded into
310
non-<productname>PostgreSQL</productname> databases. Note that
311
the restore might fail altogether if you have rearranged column order.
312
The <option>--column-inserts</option> option is safer, though even
319
<term><option>--lock-wait-timeout=<replaceable class="parameter">timeout</replaceable></option></term>
322
Do not wait forever to acquire shared table locks at the beginning of
323
the dump. Instead, fail if unable to lock a table within the specified
324
<replaceable class="parameter">timeout</>. The timeout may be
325
specified in any of the formats accepted by <command>SET
326
statement_timeout</>. Allowed values vary depending on the server
327
version you are dumping from, but an integer number of milliseconds
328
is accepted by all versions since 7.3. This option is ignored when
329
dumping from a pre-7.3 server.
335
<term><option>--no-security-labels</option></term>
338
Do not dump security labels.
344
<term><option>--no-tablespaces</option></term>
347
Do not output commands to create tablespaces nor select tablespaces
349
With this option, all objects will be created in whichever
350
tablespace is the default during restore.
356
<term><option>--no-unlogged-table-data</option></term>
359
Do not dump the contents of unlogged tables. This option has no
360
effect on whether or not the table definitions (schema) are dumped;
361
it only suppresses dumping the table data.
367
<term><option>--quote-all-identifiers</></term>
370
Force quoting of all identifiers. This may be useful when dumping a
371
database for migration to a future version that may have introduced
367
378
<term><option>--use-set-session-authorization</></term>
380
<term><option>--quote-all-identifiers</></term>
383
Force quoting of all identifiers. This may be useful when dumping a
384
database for migration to a future version that may have introduced
391
391
<term><option>-?</></term>
392
392
<term><option>--help</></term>
added
removed
doc/src/sgml/ref/pg_dumpall.sgml
