1
1
<!--
2
- $Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.55 2003/01/19 00:13:30 momjian Exp $
2
+ $Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.56 2003/02/13 04:54:15 momjian Exp $
3
3
PostgreSQL documentation
4
4
-->
5
5
@@ -283,6 +283,28 @@ PostgreSQL documentation
283
283
</listitem>
284
284
</varlistentry>
285
285
286
+ <varlistentry>
287
+ <term><option>-n <replaceable class="parameter">namespace</replaceable></option></term>
288
+ <term><option>--schema=<replaceable class="parameter">schema</replaceable></option></term>
289
+ <listitem>
290
+ <para>
291
+ Dump the contents of <replaceable class="parameter">schema</>
292
+ only. If this option is not specified, all non-system schemas
293
+ in the target database will be dumped.
294
+ </para>
295
+
296
+ <note>
297
+ <para>
298
+ In this mode, <application>pg_dump</application> makes no
299
+ attempt to dump any other database objects that may depend
300
+ upon objects in the selected schema. Therefore, there is no
301
+ guarantee that the results of a single schema dump can be
302
+ successfully restored by themselves into a clean database.
303
+ </para>
304
+ </note>
305
+ </listitem>
306
+ </varlistentry>
307
+
286
308
<varlistentry>
287
309
<term><option>-o</></term>
288
310
<term><option>--oids</></term>
@@ -380,8 +402,22 @@ PostgreSQL documentation
380
402
<term><option>--table=<replaceable class="parameter">table</replaceable></option></term>
381
403
<listitem>
382
404
<para>
383
- Dump data for <replaceable class="parameter">table</replaceable> only.
384
- </para>
405
+ Dump data for <replaceable class="parameter">table</replaceable>
406
+ only. If <literal>*</literal> is specified, all tables in the
407
+ specified database will be dumped. It is possible for there to be
408
+ multiple tables with the same name in different schemas; if that
409
+ is the case, all matching tables will be dumped.
410
+ </para>
411
+
412
+ <note>
413
+ <para>
414
+ In this mode, <application>pg_dump</application> makes no
415
+ attempt to dump any other database objects that may depend
416
+ upon the selected table. Therefore, there is no guarantee
417
+ that the results of a single table dump can be successfully
418
+ restored by themselves into a clean database.
419
+ </para>
420
+ </note>
385
421
</listitem>
386
422
</varlistentry>
387
423
@@ -495,10 +531,9 @@ PostgreSQL documentation
495
531
<term><option>--host=<replaceable class="parameter">host</replaceable></option></term>
496
532
<listitem>
497
533
<para>
498
- Specifies the host name of the machine on which the
499
- server
500
- is running. If host begins with a slash, it is used
501
- as the directory for the Unix domain socket.
534
+ Specifies the host name of the machine on which the server is
535
+ running. If the host name begins with a slash, it is used as the
536
+ directory for the Unix domain socket.
502
537
</para>
503
538
</listitem>
504
539
</varlistentry>
@@ -551,7 +586,7 @@ PostgreSQL documentation
551
586
552
587
<listitem>
553
588
<para>
554
- Default connection parameters
589
+ Default connection parameters.
555
590
</para>
556
591
</listitem>
557
592
</varlistentry>
@@ -578,11 +613,10 @@ connectDBStart() -- connect() failed: No such file or directory
578
613
579
614
<msgexplan>
580
615
<para>
581
- <application>pg_dump</application> could not attach to the
582
- PostgreSQL server on the specified host and port. If you see this message,
583
- ensure that the server
584
- is running on the proper host and that you have specified the proper
585
- port.
616
+ <application>pg_dump</application> could not connect to the
617
+ PostgreSQL server on the specified host and port. If you see this
618
+ message, ensure that the server is running on the proper host and
619
+ that you have specified the proper port.
586
620
</para>
587
621
</msgexplan>
588
622
</msgentry>
@@ -630,7 +664,7 @@ CREATE DATABASE foo WITH TEMPLATE template0;
630
664
631
665
<listitem>
632
666
<para>
633
- When doing a data only dump, <application>pg_dump</application> emits queries
667
+ When doing a data- only dump, <application>pg_dump</application> emits queries
634
668
to disable triggers on user tables before inserting the data and queries to
635
669
re-enable them after the data has been inserted. If the restore is stopped
636
670
in the middle, the system catalogs may be left in the wrong state.
0 commit comments