diff options
Diffstat (limited to 'doc/src/sgml/ref/pg_dump.sgml')
-rw-r--r-- | doc/src/sgml/ref/pg_dump.sgml | 19 |
1 files changed, 5 insertions, 14 deletions
diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml index eabdc62f820..b7aa43fc2dd 100644 --- a/doc/src/sgml/ref/pg_dump.sgml +++ b/doc/src/sgml/ref/pg_dump.sgml @@ -266,12 +266,12 @@ PostgreSQL documentation <listitem> <para> Output a <command>tar</command>-format archive suitable for input - into <application>pg_restore</application>. The tar-format is - compatible with the directory-format; extracting a tar-format + into <application>pg_restore</application>. The tar format is + compatible with the directory format: extracting a tar-format archive produces a valid directory-format archive. - However, the tar-format does not support compression and has a - limit of 8 GB on the size of individual tables. Also, the relative - order of table data items cannot be changed during restore. + However, the tar format does not support compression. Also, when + using tar format the relative order of table data items cannot be + changed during restore. </para> </listitem> </varlistentry> @@ -1088,15 +1088,6 @@ CREATE DATABASE foo WITH TEMPLATE template0; </para> <para> - Members of tar archives are limited to a size less than 8 GB. - (This is an inherent limitation of the tar file format.) Therefore - this format cannot be used if the textual representation of any one table - exceeds that size. The total size of a tar archive and any of the - other output formats is not limited, except possibly by the - operating system. - </para> - - <para> The dump file produced by <application>pg_dump</application> does not contain the statistics used by the optimizer to make query planning decisions. Therefore, it is wise to run |