| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Dave Cramer <pg(at)fastcrypt(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:41:09 |
| Message-ID: | 20080826154109.GE4920@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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)?
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2008-08-26 15:51:37 | Re: can't stop autovacuum by HUP'ing the server |
| Previous Message | Dave Cramer | 2008-08-26 15:28:03 | Re: can't stop autovacuum by HUP'ing the server |