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
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
