| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: heap vacuum & cleanup locks |
| Date: | 2011-11-08 07:26:57 |
| Message-ID: | CA+U5nM+_fa6B-ag6fY=VwRuRRuaHL=vN2BedhB3dugbWUvVdwA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Nov 8, 2011 at 2:54 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> It would still be nice to fix the case where we need to freeze a tuple
> that is on a page someone else has pinned, but I don't have any good
> ideas for how to do that.
I think we need to avoid long pin hold times generally.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2011-11-08 07:48:06 | Re: GiST for range types (was Re: Range Types - typo + NULL string constructor) |
| Previous Message | Simon Riggs | 2011-11-08 07:25:06 | Re: ProcArrayLock contention |