On Fri, Mar 7, 2008 at 3:42 PM, Hannu Krosing <[EMAIL PROTECTED]> wrote:
> > Is this something that happens only with concurrent VACUUM FULLs ? > No, its about VACUUM FULL on a system catalog which fails for some reason. The VACUUM FULL may have changed CTID of a tuple because of line pointer redirection collapse. But the change is non-transactional. The current cache invalidation mechanism can only handle transactional changes (since it does not broadcast invalidations if the transaction aborts). Hence some other backend which has cached the tuple may not see the change in CTID and fail when the cached tuple is accessed. Thanks, Pavan -- Pavan Deolasee EnterpriseDB http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
