Re: Autovacuum cancellation - Mailing list pgsql-patches

From Alvaro Herrera
Subject Re: Autovacuum cancellation
Date
Msg-id 20071026205031.GD6725@alvh.no-ip.org
Whole thread Raw
In response to Re: Autovacuum cancellation  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Autovacuum cancellation  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-patches
Tom Lane wrote:
> Gregory Stark <stark@enterprisedb.com> writes:
> > I assume the right thing happens if multiple deadlock check signals fire for
> > the same autovacuum?
>
> Multiple signals shouldn't be a problem, but late-arriving ones could be.
> It might be worth having autovac explicitly clear QueryCancelPending
> after it's finished a table, so that a SIGINT sent because of activity
> on one table couldn't force cancellation of vacuum on the next one.

Ok, committed; I snuck that in as well, but I'm not sure how to test
that it works.

I adjusted the comments -- I think they're more correct now.  I also
added a puny paragraph to lmgr/README.

--
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: Fix ecpg dependency on postgres.h
Next
From: Bruce Momjian
Date:
Subject: Re: Minor change to pg_dump docs