[pgpool-hackers: 62] Re: white/black lists for query cache

[Tatsuo Ishii]

Forwarding to the mailing list. Forgot to send uptheread to the
mailing list(my fault).
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp

> On 4/6/12 3:49 PM, Tatsuo Ishii wrote:
>>>>> I've been working on using whitelists and blacklists with the query
>>>>> cache and am wondering if there's interest in including that in the
>>>>> project.  I've been writing it against 3.1 (because that's what I had
>>>>> the source code for), so I'd need to port the changes to 3.1.2 and
>>>>> then fix an insane bug that's fairly easy to work around.
>>>>>
>>>>> If there's no interest then I'll keep it as a fork.
>>>> Thanks but it's already in git master.
>>>>
>>>> white_memqcache_table_list = ''
>>>>                                      # Comma separated list of table names to memcache
>>>>                                      # that don't write to database
>>>>                                      # Regexp are accepted
>>>> black_memqcache_table_list = ''
>>>>                                      # Comma separated list of table names not to memcache
>>>>                                      # that don't write to database
>>>>                                      # Regexp are accepted
>>> I saw that in the archives; that's table names, while mine is function
>>> names.  It's more like the load balance white/black list (and so I was
>>> able to re-use most of that code).
>> Git master automatically disables query cache if SELECT includes non
>> immutable functions. Why do you need functions white/black list?
> Now that I know that I probably don't.
> 
> 
>   alex
>