ITAGAKI Takahiro <[EMAIL PROTECTED]> 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
cancel_autovac_on_drop-2.patch
Description: Binary data
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
