From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Streaming-only Remastering |
Date: | 2012-06-15 17:10:24 |
Message-ID: | 4FDB6C80.9050200@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 6/10/12 11:47 AM, Joshua Berkus wrote:
> So currently we have a major limitation in binary replication, where it is not possible to "remaster" your system (that is, designate the most caught-up standby as the new master) based on streaming replication only. This is a major limitation because the requirement to copy physical logs over scp (or similar methods), manage and expire them more than doubles the administrative overhead of managing replication. This becomes even more of a problem if you're doing cascading replication.
>
> Therefore I think this is a high priority for 9.3.
>
> As far as I can tell, the change required for remastering over streaming is relatively small; we just need to add a new record type to the streaming protocol, and then start writing the timeline change to that. Are there other steps required which I'm not seeing?
*sound of crickets chirping*
Is there other work involved which isn't immediately apparent?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-06-15 17:45:43 | Re: sortsupport for text |
Previous Message | Tom Lane | 2012-06-15 17:04:52 | Re: Saving snapshots for later use |