Re: Feature freeze date for 8.1 - Mailing list pgsql-hackers

From Bruno Wolff III
Subject Re: Feature freeze date for 8.1
Date
Msg-id 20050429155140.GA7394@wolff.to
Whole thread Raw
In response to Re: Feature freeze date for 8.1  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Feature freeze date for 8.1  ("Marc G. Fournier" <scrappy@postgresql.org>)
List pgsql-hackers
On Fri, Apr 29, 2005 at 10:09:43 -0400, Bruce Momjian <pgman@candle.pha.pa.us> wrote:
> Tom Lane wrote:
> > Christopher Browne <cbbrowne@acm.org> writes:
> > > In the last exciting episode, pgman@candle.pha.pa.us (Bruce Momjian) wrote:
> > >> o integrated auto-vacuum (Bruce)
> > 
> > > If this can kick off a vacuum of a Very Large Table at an unfortunate
> > > time, this can turn out to be a prety painful misfeature.
> > 
> > [ shrug... ]  You'll always be able to turn it off if you don't want it.
> > I'm not sure that we'll be ready to turn it on by default even in 8.1.
> 
> Agreed.  It will just be there to turn on from postgresql.conf if you
> want it, and we do have TODO information about keeping such an FSM for
> recently expired pages.

I think if we aren't finding problems in testing that it would be better
to turn pg_autovacuum on by default. Vacuum is something the burns new
users and having it one by default is going to cut down on surprises.
Experienced users know about vacuum and will probably read the release
notes when upgrading and do something that is appropiate for them.


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [GENERAL] Returning a RECORD, not SETOF RECORD
Next
From: "Matthew T. O'Connor"
Date:
Subject: Re: Feature freeze date for 8.1