| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Steve Clark <sclark(at)netwolves(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: pg_dumpall |
| Date: | 2008-01-17 18:47:05 |
| Message-ID: | 11586.1200595625@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Tom Lane wrote:
>> That's intentional, because it doesn't. What you get is a pg_dump
>> snapshot of each database in sequence; those snapshots don't all
>> correspond to the same time instant. There isn't any good way to
>> guarantee time coherence of dumps across two databases.
> The fine point possibly being missed is that each database's dump
> produced by pg_dumpall is, of course, self-consistent.
Right, but Steve already knew that.
Hmm ... it suddenly strikes me that Simon's "transaction snapshot
cloning" idea could provide a way to get exactly coherent dumps from
multiple databases in the same cluster. Maybe he already realized that,
but I didn't.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Smith | 2008-01-17 19:08:07 | Re: pg_dumpall |
| Previous Message | Alvaro Herrera | 2008-01-17 18:43:58 | Re: pg_dumpall |