Horton

Re: First steps with 8.3 and autovacuum launcher

Simon Riggs <simon@2ndquadrant.com>

View thread View on postgr.es
From: Simon Riggs <simon@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@commandprompt.com>, Michael Paesold <mpaesold@gmx.at>, Heikki Linnakangas <heikki@enterprisedb.com>, Gregory Stark <stark@enterprisedb.com>, Guillaume Smet <guillaume.smet@gmail.com>, "Matthew T. O'Connor" <matthew@zeut.net>, Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2007-10-12T15:02:02Z
Lists: pgsql-hackers 
On Fri, 2007-10-12 at 10:19 -0400, Tom Lane wrote:
> Simon Riggs <simon@2ndquadrant.com> writes:
> > I think the best way to handle this is to have two limits.
> > First limit attempts to autovacuum, but can be cancelled.
> > When we hit second limit, sometime later, then autovacuum cannot be
> > cancelled.
> 
> This seems like uselessly complex overdesign.

OK

> In short: put in the automatic lock cancel for regular vacuums, disable
> it for antiwraparound vacuums, but don't disable manual cancels; and
> definitely don't invent a complicated new set of behaviors around that.

That seemed more complex when I thought about that, but if we just use
SIGUSR2 for automatic cancels then this would be very simple.

Or did you have another design?

-- 
  Simon Riggs
  2ndQuadrant  http://www.2ndQuadrant.com