Skip to content

Commit 095728f

Browse files
authored
Merge pull request #11216 from uncch-rdmc/11213_vacuum_full
document need for vacuum full in custom format
2 parents 57e8a13 + 4435fb2 commit 095728f

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

doc/sphinx-guides/source/admin/troubleshooting.rst

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -162,7 +162,9 @@ A full backup of the table can be made with pg_dump, for example:
162162

163163
``pg_dump <CREDENTIALS> --table=actionlogrecord --data-only <DATABASE_NAME> > /tmp/actionlogrecord_backup.sql``
164164

165-
(In the example above, the output will be saved in raw SQL format. It is portable and human-readable, but uses a lot of space. It does, however, compress very well. Add the ``-Fc`` option to save the output in a proprietary, binary format that's already compressed).
165+
In the example above, the output will be saved in raw SQL format. It is portable and human-readable, but uses a lot of space. It does, however, compress very well.
166+
167+
Add the ``-Fc`` option to save the output in a proprietary, compressed binary format which will dump and restore much more quickly, but note that in this format dead tuples will be copied as well. To reduce the amount of storage consumed by the newly-trimmed ``actionlogrecord`` table, you must issue ``vacuum full actionlogrecord`` before dumping the database in this custom format.
166168

167169

168170
Getting Help

0 commit comments

Comments
 (0)