| From: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Having query cache in core |
| Date: | 2018-05-07 07:00:20 |
| Message-ID: | 1360940e-904b-a2b4-23b2-5b34b40d102f@iki.fi |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 07/05/18 05:47, Tom Lane wrote:
> Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> writes:
>> Does anybody think having in-memory query result cache in core is a
>> good idea?
>
> No.
Agreed.
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.
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2018-05-07 07:05:20 | citext function overloads for text parameters |
| Previous Message | Shay Rojansky | 2018-05-07 06:35:15 | Re: citext function overloads for text parameters |