| From: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Subplan result caching |
| Date: | 2018-05-23 10:10:49 |
| Message-ID: | CAB=Je-E+fce=47USQ0pts350ijX32tSXkineGu9xAy8iC9a72w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>I like the idea.
+1
>Also, there probably should be a GUC for this, defaulting to "off".
I think the feature could be on by default provided it can properly
identify "volatile" functions/tables hidden behind views.
Vladimir
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Carter Thaxton | 2018-05-23 10:18:52 | Re: Add --include-table-data-where option to pg_dump, to export only a subset of table data |
| Previous Message | Laurenz Albe | 2018-05-23 10:03:30 | Re: Subplan result caching |