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

From Alvaro Herrera
Subject Re: can't stop autovacuum by HUP'ing the server
Date
Msg-id 20080826154109.GE4920@alvh.no-ip.org
Whole thread Raw
In response to Re: can't stop autovacuum by HUP'ing the server  ("Dave Cramer" <pg@fastcrypt.com>)
Responses Re: can't stop autovacuum by HUP'ing the server  ("Dave Cramer" <pg@fastcrypt.com>)
List pgsql-hackers
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)?

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


pgsql-hackers by date:

Previous
From: "Dave Cramer"
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