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

Re: 8.5 development schedule

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Greg Stark <gsstark(at)mit(dot)edu>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: 8.5 development schedule
Date: 2009-06-30 13:11:39
Message-ID: b42b73150906300611l45f188f0r4ae6dbe7046f5668@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Tue, Jun 30, 2009 at 8:12 AM, Greg Stark<gsstark(at)mit(dot)edu> wrote:
> On Tue, Jun 30, 2009 at 1:04 PM, Robert Haas<robertmhaas(at)gmail(dot)com> wrote:
>> If Hot Standby were ready to be applied, I would be all in favor of
>> that, but in fact I don't believe that's the case.  There's been no
>> movement on Hot Standby since February
>
> Well Simon was happy with it as submitted so unless people are reading
> the patch and giving feedback or using it and running into problems I
> wouldn't really expect him to make changes.
>
> That's part of the problem with leaving patches outside the source
> tree while they're being developed. It's part of what led us to
> suddenly have a massive reviewing job and making big changes in the
> final commitfest.
>
> If we apply things earlier in the cycle we can be a lot less
> conservative. We don't have to be 100% sure everything was dealt with
> in a single commit.

+1 (I'm all for getting HS in people's hands ASAP)

Given that there is also a lot of work on synchronous replication, is
it better to get the HS in so the SR stuff can use that as a baseline,
or to triage in both patches together?

merlin

In response to

Responses

pgsql-hackers by date

Next:From: Aidan Van DykDate: 2009-06-30 13:12:54
Subject: Re: pre-proposal: permissions made easier
Previous:From: Andrew DunstanDate: 2009-06-30 13:07:33
Subject: Re: pre-proposal: permissions made easier

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