| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Having query cache in core |
| Date: | 2018-05-07 18:00:54 |
| Message-ID: | 20180507180054.gn3sqxrctn4yqq3g@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2018-05-07 13:52:26 -0400, Robert Haas wrote:
> On Sun, May 6, 2018 at 10:32 PM, Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> wrote:
> > Does anybody think having in-memory query result cache in core is a
> > good idea? From the experience of implementing the feature in
> > Pgpool-II, I would think this is not terribly hard job. But first of
> > all I'm wondering if there's a demand for the feature.
>
> Caching results doesn't seem very useful to me, but caching plans
> does. I think the challenges are formidable, though.
+1
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2018-05-07 18:01:34 | Re: Cast jsonb to numeric, int, float, bool |
| Previous Message | Robert Haas | 2018-05-07 17:55:33 | Re: Built-in connection pooling |