Postgres Pro
Downloads
Home   >   mailing lists

Re: Proposal: vacuum and autovacuum parameters to control freezing - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Proposal: vacuum and autovacuum parameters to control freezing
Date
Msg-id 1162751095.3587.930.camel@silverbirch.site
Whole thread Raw
In response to Re: Proposal: vacuum and autovacuum parameters to control freezing  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Proposal: vacuum and autovacuum parameters to control freezing  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Proposal: vacuum and autovacuum parameters to control freezing  (Gregory Stark <stark@enterprisedb.com>)
List pgsql-hackers
Tree view 
On Sun, 2006-11-05 at 12:01 -0500, Tom Lane wrote:

> After re-reading the above, it strikes me that maybe names based around
> "freeze_min" and "freeze_max" would be useful?

Works for me. They are clearly related, yet different and allow a
straightforward explanation of their need and use.

e.g.

vacuum_freeze_min    The latest TransactionId that will be "frozen" during
a VACUUM is calculated by CurrentTransactionId - vacuum_freeze_min.

vacuum_freeze_max
The maximum age, calculated as distance from CurrentTransactionId, that
will be allowed before a autovacuum will be forced for that database
object.

--  Simon Riggs              EnterpriseDB   http://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: "Simon Riggs"
Date:
Subject: Re: [PATCHES] Bug in WAL backup documentation
Next
From: Tom Lane
Date:
Subject: Re: Proposal: vacuum and autovacuum parameters to control freezing