Simon Riggs wrote: > Forgive me for being dense, but what is there to stop you using a > CopySnapshot in TopMemoryContext? If you did, there would be no way to > free it, nor would we notice it had been done, AFAICS. Not anything I'm > thinking about doing, though.
Well, TopMemoryContext is no good because we want to free snapshots in a fell swoop at transaction abort. TopTransactionContext would be OK, as I just said in the parallel subthread. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-patches
