Skip site navigation (1) Skip section navigation (2)

Re: Autovacuum cancellation

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Autovacuum cancellation
Date: 2007-10-26 09:49:21
Message-ID: 87ve8uxl26.fsf@oxford.xeocode.com (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackerspgsql-patches
"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

>> I think there's a window where the process waiting directly on
>> autovacuum could have already fired its deadlock check before it was
>> waiting directly on autovacuum.
>
> I think you don't understand what that code is doing.  If there's an
> autovac anywhere in the dependency graph, it'll find it.

That'll teach me to try to read code from a patch directly without trying to
apply it or at least read the original source next to it. I thought I had seen
this code recently enough to apply the patch from memory -- clearly not.

I assume the right thing happens if multiple deadlock check signals fire for
the same autovacuum?

-- 
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com

In response to

Responses

pgsql-hackers by date

Next:From: Sebastien FLAESCHDate: 2007-10-26 10:01:34
Subject: PostgreSQL 8.3, libpq and WHERE CURRENT OF
Previous:From: Gokulakannan SomasundaramDate: 2007-10-26 09:48:50
Subject: Re: [HACKERS] Including Snapshot Info with Indexes

pgsql-committers by date

Next:From: User MkzDate: 2007-10-26 11:35:28
Subject: pgbouncer - pgbouncer: version 1.1.1
Previous:From: Heikki LinnakangasDate: 2007-10-26 09:32:09
Subject: Re: Autovacuum cancellation

pgsql-patches by date

Next:From: Heikki LinnakangasDate: 2007-10-26 10:16:41
Subject: Re: [PATCHES] Including Snapshot Info with Indexes
Previous:From: Gokulakannan SomasundaramDate: 2007-10-26 09:48:50
Subject: Re: [HACKERS] Including Snapshot Info with Indexes

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group