Re: Visibility map and freezing - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: Visibility map and freezing
Date
Msg-id 1231316492.9691.31.camel@jdavis
Whole thread Raw
In response to Re: Visibility map and freezing  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: Visibility map and freezing  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
On Wed, 2009-01-07 at 09:34 +0200, Heikki Linnakangas wrote:
> autovacuum_freeze_max_age -> autovacuum_freeze_scan_age
> vacuum_freeze_max_age    -> vacuum_freeze_scan_age
> vacuum_freeze_min_age    -> vacuum_freeze_tuple_age
> 
> *_scan_age settings control when the table is fully scanned to freeze 
> tuples and advance relfrozenxid, and vacuum_freeze_tuple_age controls 
> how old a tuple needs to be to be frozen. One objection is that you can 
> read "freeze_scan" to mean that a scan is frozen, like a tuple is 
> frozen. Any better ideas?

I see what you mean about the possible misinterpretation, but I think
it's a big improvement, and I don't have a better suggestion.

Thanks,Jeff Davis



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Visibility map and freezing
Next
From: Martin Pihlak
Date:
Subject: Re: SQL/MED dummy vs postgresql wrapper