Postgres Pro
Downloads
Home   >   mailing lists

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 491f66a50808260851w6bc09a59u2db6248610c64850@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  ("Dave Cramer" <pg@fastcrypt.com>)
Re: can't stop autovacuum by HUP'ing the server  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
Tree view


On Tue, Aug 26, 2008 at 11:41 AM, Alvaro Herrera <alvherre@commandprompt.com> wrote:
Dave Cramer wrote:
> On Tue, Aug 26, 2008 at 10:56 AM, Alvaro Herrera <alvherre@commandprompt.com

> > 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

Not only sane, but also the default ;-)

What's the max age(pg_database.datfrozenxid)?

select datfrozenxid from pg_database ;
 datfrozenxid
--------------
    201850617
    101850961
     86039359
     21522712


--
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

pgsql-hackers by date:

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