On Wed, Mar 17, 2010 at 11:42 PM, Bruce Momjian <br...@momjian.us> wrote: > Bruce Momjian wrote: >> Simon Riggs wrote: >> > On Sat, 2010-03-13 at 11:26 -0800, Josh Berkus wrote: >> > > > The list has been reduced greatly in the past week. What about HS/SR >> > > > open items? >> > > >> > > I'd like to see vacuum_defer_cleanup_age added to the "Archive" section >> > > of postgresql.conf, >> > >> > Not all parameters are in postgresql.conf.sample. Encouraging people to >> > do this is the wrong approach. >> > >> > > and add it to the docs (I'll write something this >> > > week). >> > >> > It's already in the docs, so if they read it and understand it they can >> > add it to the postgresql.conf if they so choose. >> >> I agree with Josh Berkus that vacuum_defer_cleanup_age should be in >> postgresql.conf. We don't stop listing items just because they are >> dangerous, e.g. fsync, or to discourage their use. I believe Greg Smith >> also felt it should be included. > > The bottom line is that the fact that vacuum_defer_cleanup_age is > missing from postgresql.conf is causing confusion because none of the > other settings are skipped to discourage their use. If you want to > apply that policy, we would have to revisit all the postgresql.conf > settings, and I don't think there is much interest in doing that.
I agree. If we're going to have the option, it should be in the file. ...Robert -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
