[pgpool-general: 221] Re: More information on relcache_expire

Sandeep Thakkar sandeeptt at yahoo.com
Tue Feb 14 16:51:00 JST 2012

I mean, let's say I define the value of relcache_expire as "600" seconds. and the TABLE in cache is ALTERED before that. That means my query will produce the wrong result because the relation cache is not yet updated/expired, right? On what basis one would define the value of relcache_expire in pgpool.conf?

 From: Sandeep Thakkar <sandeeptt at yahoo.com>
To: "pgpool-general at pgpool.net" <pgpool-general at pgpool.net> 
Sent: Monday, February 13, 2012 1:58 PM
Subject: [pgpool-general: 220] More information on relcache_expire

- Add relcache_expire directive to control the expiration of the internal system catalog cache. ALTER TABLE might make these cache values obsoleted and the new directive will make the risk lower(Tatsuo)
 I would like to know how to make use of this directive? A test case will help.


pgpool-general mailing list
pgpool-general at pgpool.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20120213/cc617275/attachment.html>

More information about the pgpool-general mailing list