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

From Gregory Stark
Subject Re: Proposal: vacuum and autovacuum parameters to control freezing
Date
Msg-id 87bqnlvfov.fsf@enterprisedb.com
Whole thread Raw
In response to Re: Proposal: vacuum and autovacuum parameters to control freezing  ("Simon Riggs" <simon@2ndquadrant.com>)
Responses Re: Proposal: vacuum and autovacuum parameters tocontrol freezing  ("Simon Riggs" <simon@2ndquadrant.com>)
List pgsql-hackers
"Simon Riggs" <simon@2ndquadrant.com> writes:

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

I think it's clearer if "min" and "max" are considered adjectives and always
have a subject they modify. Otherwise it's unclear what they refer to.

So "vacuum_freeze_min_age" and "vacuum_freeze_max_age" instead. 

That way it's unambiguous which is which. Ie, that it's minimum and maximum
age and not minimum and maximum transaction id which would be the other way
around.

--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Guillaume Lelarge
Date:
Subject: NULL in arrays
Next
From: Andrew Dunstan
Date:
Subject: Re: NULL in arrays