Jim Nasby <[EMAIL PROTECTED]> writes:
> On Oct 2, 2006, at 9:17 PM, Bruce Momjian wrote:
>> Jim Nasby wrote:
>>> 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.
On Oct 2, 2006, at 9:17 PM, Bruce Momjian wrote:
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 st
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 bu
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 rathe
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
> >
Jim C. Nasby wrote:
On Thu, Sep 28, 2006 at 03:07:39PM -0700, David Wheeler wrote:
PostgreSQLers,
I just ran into an issue where a client thought that autovacuum was
running but it wasn't. This is because it's not fatal when autovacuum
is on but stats_start_collector and/or stats_row_level
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 performan
On Thu, Sep 28, 2006 at 03:07:39PM -0700, David Wheeler wrote:
> PostgreSQLers,
>
> I just ran into an issue where a client thought that autovacuum was
> running but it wasn't. This is because it's not fatal when autovacuum
> is on but stats_start_collector and/or stats_row_level is off. I
>
PostgreSQLers,
I just ran into an issue where a client thought that autovacuum was
running but it wasn't. This is because it's not fatal when autovacuum
is on but stats_start_collector and/or stats_row_level is off. I
suspect that there's a reason that it's not fatal, so I thought that
it
