"Simon Riggs" <simon(at)2ndquadrant(dot)com> writes:
> vacuum_freeze_min The latest TransactionId that will be "frozen" during
> a VACUUM is calculated by CurrentTransactionId - vacuum_freeze_min.
> The maximum age, calculated as distance from CurrentTransactionId, that
> will be allowed before a autovacuum will be forced for that database
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
In response to
pgsql-hackers by date
|Next:||From: Andrew Dunstan||Date: 2006-11-05 20:33:32|
|Subject: Re: NULL in arrays|
|Previous:||From: Guillaume Lelarge||Date: 2006-11-05 19:23:59|
|Subject: NULL in arrays|
pgsql-patches by date
|Next:||From: Andrew Dunstan||Date: 2006-11-05 21:14:17|
|Subject: WIP 2 interpreters for plperl|
|Previous:||From: Tom Lane||Date: 2006-11-05 18:28:34|
|Subject: Re: Proposal: vacuum and autovacuum parameters to control freezing |