From: Bruce Momjian <bruce@momjian.us>
To: Bruce Momjian <bruce@momjian.us>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@commandprompt.com>
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: Tue, 24 Aug 2010 09:32:37 -0400 (EDT)
Message-ID: <201008241332.o7ODWbC19866@momjian.us> (raw)
In-Reply-To: <201008231924.o7NJOL616202@momjian.us>
Applied.
---------------------------------------------------------------------------
Bruce Momjian wrote:
> Tom Lane wrote:
> > Bruce Momjian <bruce@momjian.us> writes:
> > > OK, I have attached a proposed patch to improve this. I moved the
> > > pg_clog mention to a new paragraph and linked it to the reason the
> > > default is relatively low.
> >
> > The references to "vacuum freeze" are incorrect; autovacuum does NOT
> > do the equivalent of VACUUM FREEZE. Please stop playing around with
> > the perfectly good existing wording.
>
> Uh, so VACUUM FREEZE unconditionally freezes all rows, while vacuum just
> freezes rows who's xid is older than vacuum_freeze_min_age? I saw that
> in our current docs in reference to VACUUM FREEZE:
>
> Selects aggressive "freezing" of tuples. Specifying FREEZE is
> equivalent to performing VACUUM with the vacuum_freeze_min_age
> parameter set to zero. The FREEZE option is deprecated and
> will be removed in a future release; set the parameter instead.
>
> Updated patch attached.
>
> --
> Bruce Momjian <bruce@momjian.us> http://momjian.us
> EnterpriseDB http://enterprisedb.com
>
> + It's impossible for everything to be true. +
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
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: bruce@momjian.us, tgl@sss.pgh.pa.us, alvherre@commandprompt.com, josh@agliodbs.com
Subject: Re: Return of the Solaris vacuum polling problem -- anyone remember this?
In-Reply-To: <201008241332.o7ODWbC19866@momjian.us>
* 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