On Fri, Dec 31, 2010 at 8:28 AM, Alvaro Herrera <alvhe...@commandprompt.com> wrote: > A backend can have any number of snapshots registered, and those don't > allow GlobalXmin to advance. Consider an open cursor, for example. > Even if the rest of the transaction is read committed, the snapshot > registered by the open cursor still holds back GlobalXmin. My > (handwavy) idea is that whenever the transaction calls > pg_publish_snapshot(), said snapshot is registered, which makes it safe > to use even if the transaction continues to operate and obtain newer > snapshots.
Cool, even better that this is taken care of already :-) Thanks, Joachim -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
