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

From Alvaro Herrera
Subject Re: Proposal: Log inability to lock pages during vacuum
Date
Msg-id 20141021223948.GD1791@alvin.alvh.no-ip.org
Whole thread Raw
In response to Proposal: Log inability to lock pages during vacuum  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Responses Re: Proposal: Log inability to lock pages during vacuum
List pgsql-hackers
Jim Nasby wrote:

> Currently, a non-freeze vacuum will punt on any page it can't get a
> cleanup lock on, with no retry. Presumably this should be a rare
> occurrence, but I think it's bad that we just assume that and won't
> warn the user if something bad is going on.

I think if you really want to attack this problem, rather than just
being noisy about it, what you could do is to keep a record of which
page numbers you had to skip, and then once you're done with your first
scan you go back and retry the lock on the pages you skipped.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Fabrízio de Royes Mello
Date:
Subject: Re: Simplify calls of pg_class_aclcheck when multiple modes are used
Next
From: Jim Nasby
Date:
Subject: Spurious set in heap_prune_chain()