| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Turning off HOT/Cleanup sometimes |
| Date: | 2014-09-19 20:16:35 |
| Message-ID: | CA+U5nM+hcT1h=G9ViUAVVg7A-5A_KKqpBaqvm0WCSi+DG=mQsg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 19 September 2014 13:04, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> What I'm thinking about is that the smarts to enable pruning is all in
> the executor nodes. So anything that updates the catalog without
> going through the executor will never be subject to pruning. That
> includes nearly all catalog-modifying code throughout the backend.
Are you saying this is a problem or a benefit? (and please explain why).
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-09-19 20:30:34 | Re: Turning off HOT/Cleanup sometimes |
| Previous Message | Marko Tiikkaja | 2014-09-19 18:52:34 | Re: Anonymous code block with parameters |