[Pgpool-general] pgpool-II: Query cache expire time

[Arthur Turrini]

Hi,

Taiki Yamaguchi wrote:
> Hi,
> 
> On Sat, 19 May 2007 19:22:52 -0300
> Arthur Turrini <atgnbk at gmail.com> wrote:
> 
>> Hi,
>>
>> I have the following scenario, "Client A" connecting through
>> pgpool-II and "Client B" connecting directly:
>>
>> Client A: SELECT * FROM sasl.people;			(it
>> returns 30 records and get cached by pgpool) Client B: SELECT * FROM
>> sasl.people;			(it returns the same 30 records)
>> Client B: INSERT INTO sasl.people VALUES (....);	(inserts one
>> record) Client B: SELECT * FROM sasl.people;
>> (it now return 31 records) Client A: SELECT * FROM
>> sasl.people;			(it stills returns 30 records :( )
>>
>> How I can avoid that ? There's a way to set an expire time to
>> pgpool's query cache?
> 
> Unfortunately, the only way to avoid this in the current version of
> pgpool-II is to delete the cache by hand. We are planning on improving
> the query cache function in the future.
> 
> --
> Taiki Yamaguchi
> 
>> Regards,
>>
>> ---
>> Arthur Turrini.
>>
>> PS: pgpool is a great product! keep the good job!
>>

By now I'm doing this:

/* ticket: XXXX */ SELECT ...

Where XXXX is an specific number (identifier) in my program so I know where the query cache belongs to, and now I'm erasing it by
ticket/time according to my 'expiration needs'.

Thank you a lot!

Regards,

---
Arthur Turrini.