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

Tatsuo Ishii ishii at postgresql.org
Sat Jul 6 08:58:51 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.

Best reagards,
--
Tatsuo Ishii
SRA OSS LLC
English: http://www.sraoss.co.jp/index_en/
Japanese:http://www.sraoss.co.jp
-------------- next part --------------
A non-text attachment was scrubbed...
Name: v2-force_cache.patch
Type: text/x-patch
Size: 5209 bytes
Desc: not available
URL: <http://www.pgpool.net/pipermail/pgpool-hackers/attachments/20240706/9dcde48a/attachment.bin>


More information about the pgpool-hackers mailing list