Re: temporarily stop autovacuum

From: ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Tatsuo Ishii <ishii(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: temporarily stop autovacuum
Date: 2009-02-12 00:57:25
Message-ID: 20090212094649.899F.52131E4D@oss.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:

> I'm not sure that this calls for a change in autovacuum itself; it seems
> to be that whatwe really need is the ability to change postgresql.conf
> settings from the SQL interface.

Sure. 'SET GLOBAL autovacuum = off' is a TODO item.

I have another idea that autovacuum will use 'autovacuum role'
to process tables. We don't need to add syntax because we already
have per-database and per-role settings.

Something like:
ALTER ROLE autovacuum SET autovacuum = off;

We also need to adjust those variable can be set on-the-fly, though.
The current version of postgres doesn't allow to set them.
ERROR: parameter "..." cannot be changed now

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-02-12 01:24:59 Re: Fixing Grittner's planner issues
Previous Message Tom Lane 2009-02-12 00:33:46 Re: Optimization rules for semi and anti joins