On 23 October 2011 00:25, Tom Lane <[email protected]> wrote: > Joachim Wieland <[email protected]> writes: >> [ synchronized snapshots patch ] > > Applied with, um, rather extensive editorialization. > > I'm not convinced that the SSI case is bulletproof yet, but it'll be > easier to test with the code committed.
Can I ask why it doesn't return the same snapshot ID each time? Surely it can't change since you can only export the snapshot of a serializable or repeatable read transaction? A "SELECT count(pg_export_snapshot()) FROM generate_series(1,10000000);" would quickly bork the pg_snapshots directory which any user can run. -- Thom Brown Twitter: @darkixion IRC (freenode): dark_ixion Registered Linux user: #516935 EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
