Recent matview push broken with -DCLOBBER_CACHE_ALWAYS

Started by Kevin Grittnerabout 12 years ago2 messages
#1Kevin Grittner
kgrittn@ymail.com

I am investigating.

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

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

#2Kevin Grittner
kgrittn@ymail.com
In reply to: Kevin Grittner (#1)
Re: Recent matview push broken with -DCLOBBER_CACHE_ALWAYS

Kevin Grittner <kgrittn@ymail.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

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers