Robert Haas <robertmh...@gmail.com> writes:
> On Fri, Oct 21, 2011 at 11:36 AM, Tom Lane <t...@sss.pgh.pa.us> wrote:
>> 1. Restrict exported snapshots to be loaded only by transactions running
>> in the same database as the exporter. This would fix the problem, but
>> it cuts out one of the main use-cases for sync snapshots, namely getting
>> cluster-wide-consistent dumps in pg_dumpall.
> I am unexcited by #2 on usability grounds. I agree with you that #3
> might end up being a fairly small pessimization in practice, but I'd
> be inclined to just do #1 for now and revisit the issue when and if
> someone shows an interest in revamping pg_dumpall to do what you're
> proposing (and hopefully a bunch of other cleanup too).
Seems like that is the consensus view, so that's what I'll do.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
