Re: How about a option to disable autovacuum cancellation on lock conflict? - Mailing list pgsql-hackers

From Robert Haas
Subject Re: How about a option to disable autovacuum cancellation on lock conflict?
Date
Msg-id CA+TgmoaB8rnqM9fvKbER59S7VbSYvOO8ADnsV4exon3W3KqV9g@mail.gmail.com
Whole thread Raw
In response to Re: How about a option to disable autovacuum cancellation on lock conflict?  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Responses Re: How about a option to disable autovacuum cancellation on lock conflict?  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On Sat, Nov 29, 2014 at 11:46 PM, Jim Nasby <Jim.Nasby@bluetreble.com> wrote:
> What do you mean by "never succeed"? Is it skipping a large number of pages?
> Might re-trying the locks within the same vacuum help, or are the user locks
> too persistent?

You are confused.  He's talking about the relation-level lock that
vacuum attempts to take before doing any work at all on a given table,
not the per-page cleanup locks that it takes while processing each
page.  If the relation-level lock can't be acquired, the whole table
is skipped.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Review of GetUserId() Usage
Next
From: Воронин Дмитрий
Date:
Subject: Getting references for OID