On Sat, 2008-12-20 at 22:07 +0200, Heikki Linnakangas wrote: > Gregory Stark wrote: > > A vacuum being replayed -- even in a different database -- could trigger the > > error. Or with the btree split issue, a data load -- again even in a > > different > > database -- would be quite likely cause your SELECT to be killed. > > Hmm, I wonder if we should/could track the "latestRemovedXid" separately > for each database. There's no reason why we need to kill a read-only > query in database X when a table in database Y is vacuumed.
Already implemented in code. see ResolveRedoVisibilityConflicts() -- Simon Riggs www.2ndQuadrant.com PostgreSQL Training, Services and Support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
