Re: pg_dumpall - Mailing list pgsql-general

From Tom Lane
Subject Re: pg_dumpall
Date
Msg-id 11586.1200595625@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_dumpall  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-general
Alvaro Herrera <alvherre@commandprompt.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

pgsql-general by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: pg_dumpall
Next
From: Greg Smith
Date:
Subject: Re: pg_dumpall