Re: Autovacuum cancellation

From: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: Autovacuum cancellation
Date: 2007-10-26 09:32:09
Message-ID: 4721B419.1070700@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers pgsql-patches

Alvaro Herrera wrote:
> /*
> * Look for a blocking autovacuum. There will only ever
> * be one, since the autovacuum workers are careful
> * not to operate concurrently on the same table.
> */

I think that's a bit unaccurate. You could have multiple autovacuum
workers operating on different tables participating in a deadlock. The
reason that can't happen is that autovacuum never holds a lock while
waiting for another.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Gregory Stark 2007-10-26 09:49:21 Re: Autovacuum cancellation
Previous Message User Mkz 2007-10-26 09:12:33 pgbouncer - pgbouncer: fix signedness warnings in code

Browse pgsql-hackers by date

  From Date Subject
Next Message Martijn van Oosterhout 2007-10-26 09:48:23 Re: module archive
Previous Message Peter Eisentraut 2007-10-26 08:57:01 Re: module archive

Browse pgsql-patches by date

  From Date Subject
Next Message Gokulakannan Somasundaram 2007-10-26 09:48:50 Re: [HACKERS] Including Snapshot Info with Indexes
Previous Message Zdenek Kotala 2007-10-26 09:17:04 Fix ecpg dependency on postgres.h