| From: | CK Tan <cktan(at)vitessedata(dot)com> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
| Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Tom Lane <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 09:16:56 |
| Message-ID: | CAJNt7=Z_2HeGKNQUJnna+p+vhUMnft1ipPTV10e53v6vw8WdVg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, May 11, 2018, 7:13 PM Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> wrote:
> > You could probably write an extension for that, though. I think the
> > planner hook and custom scans give you enough flexibility to do that
> > without modifying the server code.
>
> Thanks for the advice. But I rather thought about bypassing the raw
> parser and the planner. i.e. use the query string (or its hash) as the
> index of the query cache.
>
I think you need to know which tables are involved and if they were
modified.
Regards,
-cktan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Khandekar | 2018-05-11 09:20:08 | Re: Needless additional partition check in INSERT? |
| Previous Message | Tatsuo Ishii | 2018-05-11 09:12:55 | Re: Having query cache in core |