pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
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 15:19:54 -0400
Message-ID: <1282590106-sup-7578@alvh.no-ip.org> (raw)
In-Reply-To: <201008231855.o7NItt310271@momjian.us>
References: <201008231855.o7NItt310271@momjian.us>

Excerpts from Bruce Momjian's message of lun ago 23 14:55:55 -0400 2010:

> 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.
> 
> Comments?

I think the new para doesn't make much sense, in context.  Why does it
say "freeze"?  How can we expect users to understand how that is
related to this parameter?

> --- 4150,4165 ----
>          <para>
>           Specifies the maximum age (in transactions) that a table's
>           <structname>pg_class</>.<structfield>relfrozenxid</> field can
> !         attain before a <command>VACUUM</> freeze operation is forced
> !         to prevent transaction ID wraparound within the table.
> !         Note that the system will launch autovacuum processes to
> !         prevent wraparound even when autovacuum is otherwise disabled.
> !        </para>
> ! 
> !        <para>
> !         Vacuum freeze also allows removal of old files from the
> !         <filename>pg_clog</> subdirectory, which is why the default
> !         is a relatively low 200 million transactions.
>           This parameter can only be set at server start, but the setting
>           can be reduced for individual tables by
>           changing storage parameters.

-- 
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support



view thread (31+ messages)  latest in thread

Message-ID: <1282590106-sup-7578@alvh.no-ip.org>
Permalink:  ../1282590106-sup-7578@alvh.no-ip.org/
Also on:    postgresql.org/message-id/1282590106-sup-7578@alvh.no-ip.org

 · 

reply

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: <1282590106-sup-7578@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