Re: Patch: Tie stats options to autovacuum in - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Patch: Tie stats options to autovacuum in
Date
Msg-id 200610030117.k931Hq629802@momjian.us
Whole thread Raw
In response to Re: Patch: Tie stats options to autovacuum in  (Jim Nasby <jim@nasby.net>)
Responses Re: Patch: Tie stats options to autovacuum in  (Jim Nasby <jim@nasby.net>)
List pgsql-hackers
Jim Nasby wrote:
> On Oct 2, 2006, at 8:41 PM, Bruce Momjian wrote:
> > David E. Wheeler wrote:
> >> On Sep 28, 2006, at 16:39, Jim C. Nasby wrote:
> >>
> >>> +1. I was just at a client today that had run into this problem.
> >>>
> >>> Actually, I'm in favor of refusing to start if autovac is on but the
> >>> proper stats settings aren't. I'd rather that then people ending up
> >>> with
> >>> bloated databases and crappy performance.
> >>
> >> I agree, but I figured that this was a start, at least.
> >
> > The problem with refusing to start is that autovacuum is sighup, so  
> > you
> > might modify postgresql.conf and do a server restart, and then the
> > server doesn't start.  Are people OK with that?
> >
> > I did apply the postgresql.conf comment addition.
> 
> Hrm... how about if the options are incompatible on HUP we refuse to  
> pick up any new settings and complain loudly?

We don't read postgresql.conf as a test and then set values.

--  Bruce Momjian   bruce@momjian.us EnterpriseDB    http://www.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: Patch: Tie stats options to autovacuum in
Next
From: Bruce Momjian
Date:
Subject: Re: [PATCHES] Bad bug in fopen() wrapper code