diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml index 3286c9575a..0f254d45ad 100644 --- a/doc/src/sgml/ref/pg_dump.sgml +++ b/doc/src/sgml/ref/pg_dump.sgml @@ -1,5 +1,5 @@ @@ -77,8 +77,8 @@ PostgreSQL documentation the custom format (). It allows for selection and reordering of all archived items, and is compressed by default. The tar format - () is not compressed and it is not possible to - reorder data when loading, but it is otherwise quite flexible; + () is not compressed and has restrictions on + reordering data when loading, but it is otherwise quite flexible; moreover, it can be manipulated with standard Unix tools such as tar. @@ -224,10 +224,11 @@ PostgreSQL documentation custom - Output a custom archive suitable for input into - pg_restore. This is the most flexible - format in that it allows reordering of loading data as well - as object definitions. This format is also compressed by default. + Output a custom-format archive suitable for input into + pg_restore. + This is the most flexible output format in that it allows manual + selection and reordering of archived items during restore. + This format is also compressed by default. @@ -237,11 +238,14 @@ PostgreSQL documentation tar - Output a tar archive suitable for input into - pg_restore. Using this archive format - allows reordering and/or exclusion of database objects - at the time the database is restored. It is also possible to limit - which data is reloaded at restore time. + Output a tar-format archive suitable for input + into pg_restore. + This output format allows manual selection and reordering of + archived items during restore, but there is a restriction: the + relative order of table data items cannot be changed during + restore. Also, tar format does not support + compression and has a limit of 8 GB on the size of individual + tables.