On Tue, Dec 18, 2012 at 5:25 PM, anara...@anarazel.de <and...@anarazel.de> wrote: > The problem is that at the time GetSnapshotData returns the xmin horizon > might have gone upwards and tuples required for decoding might get removed by > other backends. That needs to be prevented while holding the procarray lock > exclusively.
Well, for the ordinary use of GetSnapshotData(), that doesn't matter, because GetSnapshotData() also updates proc->xmin. If you're trying to store a different value in that field then of course it matters. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
