| From: | Michael Nolan <htfoot(at)gmail(dot)com> |
|---|---|
| To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Consistent state for pg_dump and pg_dumpall |
| Date: | 2015-05-20 16:24:50 |
| Message-ID: | CAOzAquJyPRRmdsoXim+sDFW9212ve9K3qQ327HjUf2bNBp9-Ng@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
The documentation for pg_dump says that dump files are created in a
consistent state.
Is that true across multiple tables in the same pg_dump command?
(Obviously it would not be true if I dumped tables using separate pg_dump
commands. But if I put the database into a backup state using
'pg_start_backup', would separately executed pg_dump commands be in a
consistent state across the set of dump files?)
The documentation for pg_dumpall does not say that its dump file is in a
consistent state (eg, across all tables), but it does say that it uses
pg_dump to dump clusters. So, how consistent are the tables in pg_dumpall
files?
--
Mike Nolan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2015-05-20 16:40:03 | Re: Consistent state for pg_dump and pg_dumpall |
| Previous Message | William Dunn | 2015-05-20 15:59:09 | Can we simulate Oracle Flashback with pg_export_snapshot()? |