From: Alvaro Herrera <alvherre@commandprompt.com>
To: Bruce Momjian <bruce@momjian.us>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: Return of the Solaris vacuum polling problem -- anyone remember this?
Date: Mon, 23 Aug 2010 12:14:52 -0400
Message-ID: <1282579975-sup-2769@alvh.no-ip.org> (raw)
In-Reply-To: <201008221651.o7MGplA28857@momjian.us>
References: <201008221651.o7MGplA28857@momjian.us>
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@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: alvherre@commandprompt.com, bruce@momjian.us, tgl@sss.pgh.pa.us, josh@agliodbs.com
Subject: Re: Return of the Solaris vacuum polling problem -- anyone remember this?
In-Reply-To: <1282579975-sup-2769@alvh.no-ip.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox