database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-27 12:41:57 +03:00
Code Activity

Make sure the pg_dump tar archiver can handle members larger than 2 GB, but

Browse Source 
does not create members larger than allowed by the tar format.  Also, fix
the generation of the tar header to conform to POSIX.
This commit is contained in:
Peter Eisentraut
2002-09-06 21:58:36 +00:00
parent 172f9a49e0
commit 38e444aae6
2 changed files with 57 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
doc/src/sgml/ref/pg_dump.sgml
View File

@ -1,5 +1,5 @@
<!--
$Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.49 2002/08/27 18:57:26 petere Exp $
$Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.50 2002/09/06 21:58:36 petere Exp $
PostgreSQL documentation
-->
@ -662,6 +662,15 @@ CREATE DATABASE foo WITH TEMPLATE = template0;
</itemizedlist>
</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 a 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>
</refsect1>
<refsect1 id="pg-dump-examples">