From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Return of the Solaris vacuum polling problem -- anyone remember this? |
Date: | 2010-08-23 16:14:52 |
Message-ID: | 1282579975-sup-2769@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Excerpts from Bruce Momjian's message of dom ago 22 12:51:47 -0400 2010:
> Well, the reason that value is 200 million is for pg_clog cleanup, not
> for xid wraparound protection. The next sentence does relate to xid
> wraparound, but it seems to fit because the previous sentence ends with
> xid wraparound:
>
> Note that the system will launch autovacuum processes to
> prevent wraparound even when autovacuum is otherwise disabled.
>
> If we were worried about just xid wraparound I assume the value would be
> 2 billion.
>
> Do you have a suggestion? Reorder the items?
I'd add another para before that one saying that this value "also"
affects pg_clog truncation. I agree that putting pg_clog truncation as
the first item here is not an improvement. For most people, having
those pg_clog files there or not is going to be a wash, compared to data
size.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-08-23 16:40:32 | Re: Return of the Solaris vacuum polling problem -- anyone remember this? |
Previous Message | Alvaro Herrera | 2010-08-23 15:49:41 | Re: WIP: extensible enums |