Tom Lane wrote:
> Gregory Stark <stark(at)enterprisedb(dot)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
In response to
pgsql-hackers by date
|Next:||From: Magnus Hagander||Date: 2007-10-26 20:52:01|
|Subject: Re: win32 threads patch vs beta2 - what to do?|
|Previous:||From: Alvaro Herrera||Date: 2007-10-26 20:45:10|
|Subject: pgsql: Allow an autovacuum worker to be interrupted automatically when |
pgsql-committers by date
|Next:||From: Magnus Hagander||Date: 2007-10-26 21:50:10|
|Subject: pgsql: Change win32 child-death tracking code to use a threadpool to |
|Previous:||From: User Dpage||Date: 2007-10-26 20:48:59|
|Subject: pginstaller - pginst: Couple o' minor fixes.|
pgsql-patches by date
|Next:||From: Bruce Momjian||Date: 2007-10-27 16:09:14|
|Subject: Re: Minor change to pg_dump docs|
|Previous:||From: Tom Lane||Date: 2007-10-26 14:19:22|
|Subject: Re: Fix ecpg dependency on postgres.h |