Re: jaguar is up

Greg Stark <stark@enterprisedb.com>

From: Gregory Stark <stark@enterprisedb.com>
To: "Tom Lane" <tgl@sss.pgh.pa.us>
Cc: <ohp@pyrenet.fr>, "pgsql-hackers list" <pgsql-hackers@postgresql.org>
Date: 2007-11-29T00:29:39Z
Lists: pgsql-hackers
"Tom Lane" <tgl@sss.pgh.pa.us> writes:

> I didn't do anything about it at the time, but now I am tempted to
> modify LookupOpclassInfo() so that CLOBBER_CACHE_ALWAYS disables
> its internal cache.  Any objections?

That sounds not equivalent to receiving a relcache flush at any particular
point in time where a relcache flush could be received. Wouldn't it make more
sense (and test more code) to go ahead and cache all the same data but flush
it whenever a relcache flush could possibly be received?

-- 
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com
  Ask me about EnterpriseDB's RemoteDBA services!