Re: bug? autovacuum is not launched even if autovacuum_freeze_max_age is reached

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: bug? autovacuum is not launched even if autovacuum_freeze_max_age is reached
Date: 2010-02-16 16:00:37
Message-ID: 29631.1266336037@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:
> Fujii Masao escribi:
>> In HEAD, when autovacuum is disabled, autovacuum process is not
>> launched forcibly to prevent XID wraparound even if we go through
>> autovacuum_freeze_max_age. This seems to be because
>> ShmemVariableCache->xidVacLimit is not initialized (i.e.,
>> SetTransactionIdLimit() is not called) until VACUUM is performed.
>>
>> OTOH, in older version, ShmemVariableCache->xidVacLimit is always
>> initialized when backend updates the flat database file, and then
>> autovacuum process seems to be launched forcibly as expected.

> Hmm. Yeah, this is a serious problem.

I thought I had put in some workaround for that when I did the flat
file changes. I don't remember what though, and it's evidently
broken now in any case.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Sabino Mullane 2010-02-16 16:02:52 Re: Listen / Notify - what to do when the queue is full
Previous Message Hitoshi Harada 2010-02-16 15:55:38 Re: ToDo: plpgsql plugin for query and expression verification