From: Tom Lane Date: Sat, 15 May 2010 18:11:41 +0000 (+0000) Subject: Improve documentation of pg_restore's -l and -L switches to point out their X-Git-Tag: REL7_4_30~34 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=00a80128eac6d7d56ee7481059ccc400ef64529a;p=thirdparty%2Fpostgresql.git Improve documentation of pg_restore's -l and -L switches to point out their interactions with filtering switches, such as -n and -t. Per a complaint from Russell Smith. --- diff --git a/doc/src/sgml/ref/pg_restore.sgml b/doc/src/sgml/ref/pg_restore.sgml index 88319e2e344..3293abb3919 100644 --- a/doc/src/sgml/ref/pg_restore.sgml +++ b/doc/src/sgml/ref/pg_restore.sgml @@ -1,4 +1,4 @@ - + @@ -156,10 +156,7 @@ t - The archive is a tar archive. Using this - archive format allows reordering and/or exclusion of schema - elements at the time the database is restored. It is also - possible to limit which data is reloaded at restore time. + The archive is a tar archive. @@ -169,10 +166,7 @@ The archive is in the custom format of - pg_dump. This is the most - flexible format in that it allows reordering of data load - as well as schema elements. This format is also compressed - by default. + pg_dump. @@ -207,8 +201,9 @@ List the contents of the archive. The output of this operation - can be used with the option to restrict - and reorder the items that are restored. + can be used as input to the option. Note that + if filtering switches such as @@ -218,11 +213,18 @@ - Restore elements in list-file only, and in the - order they appear in the file. Lines can be moved and may also - be commented out by placing a ; at the - start of the line. (See below for examples.) + Restore only those archive elements that are listed in list-file, and restore them in the + order they appear in the file. Note that + if filtering switches such as + + list-file is normally created by + editing the output of a previous