Re: is sync rep stalled? - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: is sync rep stalled?
Date
Msg-id 1285834482.1921.454.camel@ebony
Whole thread Raw
In response to Re: is sync rep stalled?  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: is sync rep stalled?  (David Fetter <david@fetter.org>)
Re: is sync rep stalled?  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
On Thu, 2010-09-30 at 09:09 +0300, Heikki Linnakangas wrote:
> On 29.09.2010 10:56, Fujii Masao wrote:
> > On Wed, Sep 29, 2010 at 11:47 AM, Robert Haas<robertmhaas@gmail.com>  wrote:

> >> This feature is important, and we need to get it done.  How do we get
> >> the ball rolling again?
> 
> Agreed. Actually, given the lack of people jumping in and telling us 
> what they'd like to do with the feature, maybe it's not that important 
> after all.

I don't see anything has stalled. I've been busy for a few days, so
haven't had a chance to follow up on the use cases, as suggested. I'm
busy again today, so cannot reply further. Anyway, taking a few days to
let us think some more about the technical comments is no bad thing.

I think we need to relax about this feature some more because trying to
get something actually done when basic issues need analysis is hard and
that creates tension. Between us we can work out the code in a few days,
once we know which code to write.

What we actually need to do is talk and listen. I'd like to suggest that
we have an online "focus day" (onlist) on Sync Rep on Oct 5 and maybe 6
as well?. Meeting in person is possible, but probably impractical. But a
design sprint, not a code sprint. 

This is important and I'm sure we'll work something out. 

-- Simon Riggs           www.2ndQuadrant.comPostgreSQL Development, 24x7 Support, Training and Services



pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Fw: patch for pg_ctl.c to add windows service start-type
Next
From: Bernd Helmle
Date:
Subject: Re: starting to review the Extend NOT NULL representation to pg_constraint patch