| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Having query cache in core |
| Date: | 2018-05-07 17:52:26 |
| Message-ID: | CA+TgmobAkqOwTHuy+30oirrkif1jXiyjfOtY5NTr1wfWxTGEzA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2018-05-07 17:55:33 | Re: Built-in connection pooling |
| Previous Message | Robert Haas | 2018-05-07 17:49:35 | Re: Explain buffers wrong counter with parallel plans |