Skip site navigation (1) Skip section navigation (2)

Re: damage control mode

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Greg Smith <greg(at)2ndquadrant(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, David Fetter <david(at)fetter(dot)org>, Josh Berkus <josh(at)agliodbs(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: damage control mode
Date: 2010-01-12 04:44:30
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Mon, Jan 11, 2010 at 11:15 PM, Greg Smith <greg(at)2ndquadrant(dot)com> wrote:
> Personally, I'd like the topic of a thread on "damage control" to be all
> about testing the one big patch that's already in there (HS), its related
> bits like the VACUUM FULL changes, and potentially SR too.  Those are things
> that are touching internals that can introduce all sorts of new bugs, in the
> same way that the FSM changes were pretty scary for 8.4.  Those are the
> things I worry about every day right now, not whether, say, a very
> walled-off indexing change for data that only a fraction of the user base
> uses might destabilize things.  Getting excited about pre-emptively kicking
> out patches that may not even be commit candidates anyway is distracting
> thought from the stuff that really matters right now IMHO.  I'm more
> concerned about how to reach a bug list as mature as the one Tom presented
> at the end of March last year earlier in this one, for the features that are
> already in there.

I agree.  My main concern in terms of dealing with these outstanding
is that it will distract us, particularly Tom, from stabilizing the
tree, especially HS, VF, and SR.  If the tree were in a releasable
state today I wouldn't be worrying about it.


In response to


pgsql-hackers by date

Next:From: Dave PageDate: 2010-01-12 04:54:03
Subject: Re: mailing list archiver chewing patches
Previous:From: Greg SmithDate: 2010-01-12 04:24:24
Subject: Re: Streaming replication status

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group