Re: Recent matview push broken with -DCLOBBER_CACHE_ALWAYS

From: Kevin Grittner <kgrittn(at)ymail(dot)com>
To: Kevin Grittner <kgrittn(at)ymail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Recent matview push broken with -DCLOBBER_CACHE_ALWAYS
Date: 2013-11-06 18:38:40
Message-ID: 1383763120.28519.YahooMailNeo@web162906.mail.bf1.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Kevin Grittner <kgrittn(at)ymail(dot)com> wrote:

> I am investigating.

Information from the syscache entry for the table was being
referenced after the relation was closed.  We were generally
getting away with it until the new locking caused a check for
invalidation messages at a new spot.  Moving the heap_close() call
down a few lines fixed it by keeping the syscache entry valid until
we were through with it.

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kohei KaiGai 2013-11-06 19:12:06 Re: [v9.4] row level security
Previous Message Josh Berkus 2013-11-06 18:14:35 Re: [v9.4] row level security