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

Re: damage control mode

From: David Fetter <david(at)fetter(dot)org>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: damage control mode
Date: 2010-01-08 02:09:13
Message-ID: 20100108020913.GN30864@fetter.org (view raw or flat)
Thread:
Lists: pgsql-hackers
On Thu, Jan 07, 2010 at 08:57:15PM -0500, Robert Haas wrote:
> On Thu, Jan 7, 2010 at 4:23 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> >> On Thu, Jan 7, 2010 at 3:36 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >>> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> >>>> I am tempted to say we should clamp down and go into damage control
> >>>> mode sooner rather than later.
> >>>
> >>> The more I see of the HS patch, the more I think the same.  But my
> >>> proposal for "damage control mode" would be to immediately punt
> >>> everything else to the next release and focus our energies exclusively
> >>> on HS *and* SR.
> >
> >> Hmm.  There's something to what you say, but what about the people who
> >> were expecting their patches to be reviewed and perhaps committed in
> >> the forthcoming CommitFest.  I proposed a schedule for this release
> >> that involved only three CommitFests and it was rejected, so it seems
> >> a bit unfair to pull the rug out from under people at the eleventh
> >> hour.  Will we lose developers if we do this?
> >
> > Well, I think we should put at least some effort into clearing out
> > the underbrush.  There's a lot of pretty small stuff in the January CF
> > list that I think we could go through in a short time.  The biggies,
> > IMO, are the ones you noted:
> >
> >> Unfortunately, there are some patches that I probably will not feel
> >> confident to commit without your input - in particular, writeable
> >> CTEs, listen/notify, more frame options in window functions -
> >
> > and Teodor's GIN/GIST stuff.  If we feel that we are in schedule
> > trouble I think that bumping these to the next release is by far
> > the sanest response.  Bumping SR so we can get these in would be
> > completely misguided.
> 
> OK, we have a proposal on the table to bump some patches from this
> CommitFest to free up more committer resources, particularly Tom, to
> work on Hot Standby and Streaming Replication and attempt to
> accelerate the process of getting 8.5 out the door.  This proposal
> needs input from the community.  The affected patches are:

I don't see any need to thump the panic button today.

If we *must* have SR and it's not in by the 15th, let's do another
Commitfest rather than jack the people who played by the rules.

Cheers,
David.
-- 
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778  AIM: dfetter666  Yahoo!: dfetter
Skype: davidfetter      XMPP: david(dot)fetter(at)gmail(dot)com
iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate

In response to

Responses

pgsql-hackers by date

Next:From: Andrew DunstanDate: 2010-01-08 02:11:16
Subject: Re: damage control mode
Previous:From: Robert HaasDate: 2010-01-08 02:02:52
Subject: Re: Serializable implementation

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