Re: can't stop autovacuum by HUP'ing the server

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Dave Cramer <pg(at)fastcrypt(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: can't stop autovacuum by HUP'ing the server
Date: 2008-08-26 17:00:48
Message-ID: 10178.1219770048@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> If it doesn't ignore them, then it should be properly vacuuming
> template0 as any other database. We've changed autovac's behavior on
> this area back and forth so I may be misremembering what's our rationale
> du jour.

AFAICS, the only way in which current autovac treats !datallowconn
databases specially is this test in do_autovacuum:

if (dbForm->datistemplate || !dbForm->datallowconn)
default_freeze_min_age = 0;
else
default_freeze_min_age = vacuum_freeze_min_age;

Perhaps there's something wrong with the idea of setting freeze_min_age
to zero?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2008-08-26 17:06:01 Re: Split up the wiki TODO page?
Previous Message Dave Cramer 2008-08-26 16:58:59 Re: can't stop autovacuum by HUP'ing the server