[pgpool-hackers: 4523] Re: Comment to force query cache

Tatsuo Ishii ishii at postgresql.org
Sun Sep 29 08:22:42 JST 2024


>>> There is a feature request from a user.
>>> 
>>> https://github.com/pgpool/pgpool2/issues/56
>>> 
>>> That is, to allow to use SQL comment to force to create a query cache
>>> entry. We already have /*NO QUERY CACHE*/ comment, which
>>> unconditionally disabling query cache. The request is just opposite. I
>>> think this is a useful feature because in some cases there's no
>>> workaround to create query cache. I proposed a workaround to use view,
>>> but it has its own downside. See the issue for more details.
>>> 
>>> So my proposal is to support a new comment "/*FORCE QUERY CACHE*/". If
>>> a query starts with the comment, the query will be cached
>>> unconditionally. Patch attached. Comments and suggestions are welcome.
>> 
>> Attached is v2 patch. Differences from v1 are:
>> - Add regression test
>> - Tweak wording of document.
> 
> Attached is v3 patch. Differences from v2 are:
> - Rebase.
> - Add Japanese document.
> 
> If there's no objection, I will push to master branch only as this is
> a new feature for the upcoming pgpool major release.

v3 patch pushed.

Best reagards,
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp


More information about the pgpool-hackers mailing list