Re: [HACKERS] Proposal: vacuum and autovacuum parameters tocontrol freezing

2006-11-05 Thread Tom Lane
"Simon Riggs" <[EMAIL PROTECTED]> writes:
> On Sun, 2006-11-05 at 14:47 -0500, Gregory Stark wrote:
>> 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.

> Sounds logical. Hadn't seen that you could take it both ways.

Agreed --- I've adopted Greg's suggestion.

regards, tom lane

---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
   subscribe-nomail command to [EMAIL PROTECTED] so that your
   message can get through to the mailing list cleanly


Re: [HACKERS] Proposal: vacuum and autovacuum parameters tocontrol freezing

2006-11-05 Thread Simon Riggs
On Sun, 2006-11-05 at 14:47 -0500, Gregory Stark wrote:
> "Simon Riggs" <[EMAIL PROTECTED]> 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.

Sounds logical. Hadn't seen that you could take it both ways.

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



---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
   subscribe-nomail command to [EMAIL PROTECTED] so that your
   message can get through to the mailing list cleanly