Re: Concurrent HOT Update interference - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Concurrent HOT Update interference
Date
Msg-id CA+U5nMKDvraqePORoDxtNL3V32X_W68eJRAku9QPrjSYzPDi6A@mail.gmail.com
Whole thread Raw
In response to Re: Concurrent HOT Update interference  (Merlin Moncure <mmoncure@gmail.com>)
List pgsql-hackers
On 10 May 2013 15:04, Merlin Moncure <mmoncure@gmail.com> wrote:

> right. hm,   I guess this is something to keep in mind if you start
> going down the path of 'keep frequently accessed buffers pinned for
> longer durations -- possibly even forever'.

Just to mention that this scenario effectively starves anybody wanting
a cleanup lock, which was the reason we put in logic to VACUUM to skip
busy pages.

We just need to extend that thought to page level cleanup also.

--Simon Riggs                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Bug in VACUUM reporting of "removed %d row versions" in 9.2+
Next
From: Simon Riggs
Date:
Subject: Re: Concurrent HOT Update interference