Re: Shared invalidation cache messages for temporary tables - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Shared invalidation cache messages for temporary tables
Date
Msg-id 201103141242.p2ECg9J26347@momjian.us
Whole thread Raw
In response to Re: Shared invalidation cache messages for temporary tables  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Shared invalidation cache messages for temporary tables
List pgsql-hackers
Simon Riggs wrote:
> On Fri, 2011-03-11 at 20:44 -0500, Bruce Momjian wrote:
> > Looking at the code, it seems we create shared invalidation messages for
> > temporary table activity?  Is this true?  Should we be avoiding it?
> > 
> > I tested this by reviewing the code and checking calls to
> > CacheInvalidateHeapTuple(), which happens for temporary table
> > creation/destruction.
> 
> Yes, that gets called.
> 
> But in PrepareForTupleInvalidation() we ignore everything apart from
> system relations, as the first check.

OK, so this is no problem?  There is no optimization needed here? 
Thanks.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: On-the-fly index tuple deletion vs. hot_standby
Next
From: Robert Haas
Date:
Subject: Re: Macros for time magic values