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

[Tatsuo Ishii]

>> 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.

Best reagards,
--
Tatsuo Ishii
SRA OSS K.K.
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp
-------------- next part --------------
A non-text attachment was scrubbed...
Name: v3-force_cache.patch
Type: text/x-patch
Size: 9837 bytes
Desc: not available
URL: <http://www.pgpool.net/pipermail/pgpool-hackers/attachments/20240924/4c4f5faf/attachment.bin>