Skip site navigation (1) Skip section navigation (2)

Re: can't stop autovacuum by HUP'ing the server

From: "Dave Cramer" <pg(at)fastcrypt(dot)com>
To: "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: can't stop autovacuum by HUP'ing the server
Date: 2008-08-26 15:51:37
Message-ID: 491f66a50808260851w6bc09a59u2db6248610c64850@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Tue, Aug 26, 2008 at 11:41 AM, Alvaro Herrera <alvherre(at)commandprompt(dot)com
> wrote:

> Dave Cramer wrote:
> > On Tue, Aug 26, 2008 at 10:56 AM, Alvaro Herrera <
> alvherre(at)commandprompt(dot)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
>

In response to

Responses

pgsql-hackers by date

Next:From: Dave CramerDate: 2008-08-26 15:56:51
Subject: Re: can't stop autovacuum by HUP'ing the server
Previous:From: Alvaro HerreraDate: 2008-08-26 15:41:09
Subject: Re: can't stop autovacuum by HUP'ing the server

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group