Re: can't stop autovacuum by HUP'ing the server - Mailing list pgsql-hackers

From Dave Cramer
Subject Re: can't stop autovacuum by HUP'ing the server
Date
Msg-id 491f66a50808260828h7b878d51k4619d002f45adb37@mail.gmail.com
Whole thread Raw
In response to Re: can't stop autovacuum by HUP'ing the server  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: can't stop autovacuum by HUP'ing the server  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers


On Tue, Aug 26, 2008 at 10:56 AM, Alvaro Herrera <alvherre@commandprompt.com> wrote:
Dave Cramer wrote:
> On Tue, Aug 26, 2008 at 9:59 AM, Dave Cramer <pg@fastcrypt.com> wrote:
>
> > On Tue, Aug 26, 2008 at 9:37 AM, Alvaro Herrera <
> > alvherre@commandprompt.com> wrote:

> >> Certainly not, and that's not what I see here either.  I assume process
> >> 25407 is (was) the postmaster, yes?
> >>
> >> If you "show autovacuum", is it on?
> >
> > Yes that was the postmaster, and I did check to see if autovacuum was on,
> > and it was not.
> >
> So where do we go from here ?

The only possible explanation for this behavior is that somebody is
signalling the postmaster due to Xid wraparound issues.  This is keyed
on some GUC vars -- Perhaps you have autovacuum_freeze_max_age set to an
insane value?

Doesn't appear to be insane ?

#autovacuum_freeze_max_age = 200000000  # maximum XID age before forced vacuum

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: can't stop autovacuum by HUP'ing the server
Next
From: Alvaro Herrera
Date:
Subject: Re: can't stop autovacuum by HUP'ing the server