On Sun, 2006-11-05 at 12:01 -0500, Tom Lane wrote:

> After re-reading the above, it strikes me that maybe names based around
> "freeze_min" and "freeze_max" would be useful?

Works for me. They are clearly related, yet different and allow a
straightforward explanation of their need and use.

e.g.

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.

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



---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match