Re: Feature Request: pg_replication_master() - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Feature Request: pg_replication_master()
Date
Msg-id CA+U5nM+d6dQw_aoF7F_1GDgfaZoLzWseqM2FQ0DFDx+UZDfB6w@mail.gmail.com
Whole thread Raw
In response to Re: Feature Request: pg_replication_master()  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Feature Request: pg_replication_master()  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
On 24 December 2012 15:48, Bruce Momjian <bruce@momjian.us> wrote:
> On Mon, Dec 24, 2012 at 03:13:59PM +0000, Simon Riggs wrote:
>> I don't think that represents enough change to keep people happy, but
>> I don't see anything else useful being suggested in this patch. Other
>> design thoughts welcome, but personally, I think rushing this design
>> through at this stage is likely to require us to change the design
>> again in later releases.
>
> Simon, you just agreed to:
>
>> At this point, backward compatibility seems to be hampering our ability
>> to move forward.  I would like a vote that supports creation of a new
>> method for setting up streaming replication/point-in-time-recovery,
>> where backward compatibility is considered only where it is minimally
>> invasive.
>
> Let's figure out the API we want and implement it.

That's exactly what I spent the afternoon doing.

Merry Christmas

-- Simon Riggs                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Greg Smith
Date:
Subject: Re: buffer assertion tripping under repeat pgbench load
Next
From: Tom Lane
Date:
Subject: Re: buffer assertion tripping under repeat pgbench load