Re: [HACKERS] autovacuum_freeze_max_age

2007-11-10 Thread Jacques Caron
Hi Tom, At 02:51 10/11/2007, Tom Lane wrote: Uh, no, it's called only when we've advanced datfrozenxid, which is a pretty uncommon event. So I think the real hole in the proposal is that there would be a long and not-very-predictable delay between changing the parameter and having it really tak

Re: [HACKERS] autovacuum_freeze_max_age

2007-11-09 Thread Tom Lane
Jacques Caron <[EMAIL PROTECTED]> writes: > I was wondering why autovacuum_freeze_max_age actually can't be set > at runtime... guc.c points to varsup.c which says: Hmm. The original worry was that different uses might be out of sync, but right offhand it doesn't look like anything catastrophic

[HACKERS] autovacuum_freeze_max_age

2007-11-09 Thread Jacques Caron
Hi, I was wondering why autovacuum_freeze_max_age actually can't be set at runtime... guc.c points to varsup.c which says: * Note: autovacuum_freeze_max_age is a PGC_POSTMASTER parameter so that * we don't have to worry about dealing with on-the-fly changes in its