Postgres Pro
Downloads
Home   >   mailing lists

Re: Cancel autovacuum conflicting with DROP TABLE - Mailing list pgsql-patches

From ITAGAKI Takahiro
Subject Re: Cancel autovacuum conflicting with DROP TABLE
Date
Msg-id 20070622105344.6118.ITAGAKI.TAKAHIRO@oss.ntt.co.jp
Whole thread Raw
In response to Cancel autovacuum conflicting with DROP TABLE  (ITAGAKI Takahiro <itagaki.takahiro@oss.ntt.co.jp>)
Responses Re: Cancel autovacuum conflicting with DROP TABLE
List pgsql-patches
Tree view 
ITAGAKI Takahiro <itagaki.takahiro@oss.ntt.co.jp> wrote:

> Here is a patch that cancels autovacuum workers conflicting with
> DROP TABLE, TRUNCATE and CLUSTER. It was discussed here:
> http://archives.postgresql.org/pgsql-hackers/2007-06/msg00556.php

I made an adjustment for the latest 'more autovacuum fixes' patch.
http://archives.postgresql.org/pgsql-patches/2007-06/msg00217.php

Now, autovacuum workers handles ProcDie signals using ERROR
instead of FATAL. The exception is caught by the worker and
converted to the following logs.

  SIGINT -- Cancel the current job.
      LOG: autovacuum on <db>.<schema>.<table> is canceled
  SIGTERM -- Cancel all jobs.
      LOG: autovacuum on <db> is canceled

We are planning to ship 8.3 with autovacuum=on, so users will be
more likely to see conflicts between autovacuum and their commands.
This makes autovacuum more gentle.

Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center
Attachment

pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: psql: flush output in cursor-fetch mode
Next
From: Neil Conway
Date:
Subject: Re: psql: flush output in cursor-fetch mode