Re: (auto)vacuum truncate exclusive lock - Mailing list pgsql-hackers

From Tom Lane
Subject Re: (auto)vacuum truncate exclusive lock
Date
Msg-id 20824.1365787288@sss.pgh.pa.us
Whole thread Raw
In response to Re: (auto)vacuum truncate exclusive lock  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
Andres Freund <andres@2ndquadrant.com> writes:
> On 2013-04-12 13:09:02 -0400, Tom Lane wrote:
>> However, we're still thinking too small.  I've been wondering whether we
>> couldn't entirely remove the dirty, awful kluges that were installed in
>> the lock manager to kill autovacuum when somebody blocked behind it.
>> This mechanism should ensure that AV never takes an exclusive lock
>> for long enough to be a serious problem, so do we need that anymore?

> Wouldn't that make DROP TABLE stop working while autovac is processing
> the table?

Meh ... I guess you're right.  I wasn't thinking about exclusive locks
being taken elsewhere.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Kevin Grittner
Date:
Subject: Re: (auto)vacuum truncate exclusive lock
Next
From: Bruce Momjian
Date:
Subject: Re: Enabling Checksums