Dave Cramer wrote: > On Tue, Aug 26, 2008 at 10:56 AM, Alvaro Herrera <[EMAIL PROTECTED]
> > 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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers