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.
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2008-12-20 21:35:39|
|Subject: Re: dblink vs SQL/MED |
|Previous:||From: Magnus Hagander||Date: 2008-12-20 19:08:00|
|Subject: Re: [COMMITTERS] pgsql: Append major version number and
for libraries soname major|