Matthew T. O'Connor wrote: > Alvaro Herrera wrote: > >Tom Lane wrote: > >>Alvaro Herrera <[EMAIL PROTECTED]> writes: > >>>But this is misleading (started postmaster with good value, then edited > >>>postgresql.conf and entered "-2"): > >>>17903 LOG: received SIGHUP, reloading configuration files > >>>17903 LOG: -2 is outside the valid range for parameter > >>>"autovacuum_vacuum_cost_limit" (-1 .. 1000) > >>>Note how it still says the range is -1 .. 1000. > >>Can we redefine things to make zero be the "disabled" value, thus > >>keeping the range of valid values contiguous? > > > >That would be another solution ... though it would be different from the > >valid value for autovacuum_vacuum_cost_delay (on which 0 is a valid > >value). Also it would be a different value from previous versions. > > > >I don't think either of these is a showstopper, so let's go for that if > >nobody objects. > > Can you make 0 and -1 both valid disabled values? That way it will be > compatible with previous releases.
Heh, sure, we can do that too and it doesn't seem like anybody would object. I will patch the documentation so that that the "disabled" value is zero, and still allow -1. That way it doesn't seem like there should be any objection. -- Alvaro Herrera http://www.flickr.com/photos/alvherre/ "Escucha y olvidarás; ve y recordarás; haz y entenderás" (Confucio) ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend
