| From: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
|---|---|
| To: | sitnikov(dot)vladimir(at)gmail(dot)com |
| Cc: | ishii(at)sraoss(dot)co(dot)jp, cktan(at)vitessedata(dot)com, hlinnaka(at)iki(dot)fi, tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Having query cache in core |
| Date: | 2018-05-11 15:55:35 |
| Message-ID: | 20180512.005535.1387864539744910247.t-ishii@sraoss.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>> If any of the tables were modified, cache entries using the table must be
> removed.
>> (these are already implemented in Pgpool-II's in memory query cache)
>
> How do you identify updates made from a pl/pgsql procedure?
Pgpool-II does not invalidate query cache in that case.
I think in-core query cache could deal with the case (probably as
Michael suggested).
Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp
| From | Date | Subject | |
|---|---|---|---|
| Next Message | CK Tan | 2018-05-11 16:00:18 | Re: Having query cache in core |
| Previous Message | Alvaro Herrera | 2018-05-11 15:09:58 | Re: PANIC during crash recovery of a recently promoted standby |