Re: can't stop autovacuum by HUP'ing the server
От | Dave Cramer |
---|---|
Тема | Re: can't stop autovacuum by HUP'ing the server |
Дата | |
Msg-id | 491f66a50808260851w6bc09a59u2db6248610c64850@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: can't stop autovacuum by HUP'ing the server (Alvaro Herrera <alvherre@commandprompt.com>) |
Ответы |
Re: can't stop autovacuum by HUP'ing the server
Re: can't stop autovacuum by HUP'ing the server |
Список | pgsql-hackers |
On Tue, Aug 26, 2008 at 11:41 AM, Alvaro Herrera <alvherre@commandprompt.com> wrote:
select datfrozenxid from pg_database ;
datfrozenxid
--------------
201850617
101850961
86039359
21522712
> > The only possible explanation for this behavior is that somebody isNot only sane, but also the default ;-)
> > 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
What's the max age(pg_database.datfrozenxid)?
select datfrozenxid from pg_database ;
datfrozenxid
--------------
201850617
101850961
86039359
21522712
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
В списке pgsql-hackers по дате отправления: