Alvaro Herrera wrote:
> 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.
>
> What about shared catalogs?
True, vacuums on shared catalogs would affect read-only queries on all
databases.
-- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com
