On Tue, Nov 15, 2016 at 3:55 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Account for catalog snapshot in PGXACT->xmin updates. > > The CatalogSnapshot was not plugged into SnapshotResetXmin()'s accounting > for whether MyPgXact->xmin could be cleared or advanced. In normal > transactions this was masked by the fact that the transaction snapshot > would be older, but during backend startup and certain utility commands > it was possible to re-use the CatalogSnapshot after MyPgXact->xmin had > been cleared, meaning that recently-deleted rows could be pruned even > though this snapshot could still see them, causing unexpected catalog > lookup failures. This effect appears to be the explanation for a recent > failure on buildfarm member piculet. > > To fix, add the CatalogSnapshot to the RegisteredSnapshots heap whenever > it is valid.
It seems to me that this makes it possible for ThereAreNoPriorRegisteredSnapshots() to fail spuriously. The only core code that calls that function is in copy.c, and apparently we never reach that point with the catalog snapshot set. But that seems fragile. -- 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
