| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com>, 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 21:45:10 |
| Message-ID: | CA+U5nMJH6yf4q-eM2G7O0VLTw9yuX2aMZmqVHU0-U-ex3FFtWw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 19 September 2014 15:35, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Having said that, this could reasonably be considered outside the scope
> of a patch that's trying to improve the behavior for user queries.
> But if the patch author doesn't want to expand the scope like that,
> ISTM he ought to ensure that the behavior *doesn't* change for system
> accesses, rather than trying to convince us that disabling HOT for
> system updates is a good idea.
As I said, I could make an argument to go either way, so I was unsure.
I'm happy to avoid changing behaviour for catalog scans in this patch.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-09-19 21:48:23 | Re: Turning off HOT/Cleanup sometimes |
| Previous Message | Andres Freund | 2014-09-19 21:42:08 | Re: Turning off HOT/Cleanup sometimes |