Re: Proposal: Log inability to lock pages during vacuum - Mailing list pgsql-hackers

From Greg Stark
Subject Re: Proposal: Log inability to lock pages during vacuum
Date
Msg-id CAM-w4HOxRBB8ps1PNQSZkNoq6dyRfsqmMNG5dXfFGypCSvGc2w@mail.gmail.com
Whole thread Raw
In response to Re: Proposal: Log inability to lock pages during vacuum  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: Proposal: Log inability to lock pages during vacuum  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Re: Proposal: Log inability to lock pages during vacuum  (Andres Freund <andres@2ndquadrant.com>)
Re: Proposal: Log inability to lock pages during vacuum  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On Thu, Nov 6, 2014 at 9:30 PM, Andres Freund <andres@2ndquadrant.com> wrote:
> I think the retry logical is a largely pointless complication of already
> complex enough code. You're fixing a problem for which there is
> absolutely no evidence of its existance. Yes, this happens
> occasionally. But it's going to be so absolutely minor in comparison to
> just about every other source of bloat.

I agree bloat isn't really a threat, but what about the relfrozenxid?
If we skip even one page we don't get to advance it and retrying could
eliminate those skipped pages and allow us to avoid a vacuum freeze
which can be really painful. Of course that only works if you can be
sure you haven't overflowed and forgotten any skipped pages and if you
don't find the page still pinned every time until you eventually give
up on it.

-- 
greg



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: split builtins.h to quote.h
Next
From: Jim Nasby
Date:
Subject: Re: Proposal: Log inability to lock pages during vacuum