Re: WIP patch for parallel pg_dump - Mailing list pgsql-hackers

From marcin mank
Subject Re: WIP patch for parallel pg_dump
Date
Msg-id AANLkTikOrY05Y5m6Zf0gOebAWeTqzozDYKbkB6Uf6CZw@mail.gmail.com
Whole thread Raw
In response to Re: WIP patch for parallel pg_dump  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: WIP patch for parallel pg_dump  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Re: WIP patch for parallel pg_dump  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sun, Dec 5, 2010 at 7:28 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> IIRC, in old discussions of this problem we first considered allowing
> clients to pull down an explicit representation of their snapshot (which
> actually is an existing feature now, txid_current_snapshot()) and then
> upload that again to become the active snapshot in another connection.

Could a hot standby use such a snapshot representation? I.e. same
snapshot on the master and the standby?

Greetings
Marcin Mańk


pgsql-hackers by date:

Previous
From: Florian Pflug
Date:
Subject: Re: serializable read only deferrable
Next
From: Tom Lane
Date:
Subject: Re: We really ought to do something about O_DIRECT and data=journalled on ext4