From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Joshua Berkus <josh(at)agliodbs(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Streaming-only Remastering |
Date: | 2012-06-15 22:53:42 |
Message-ID: | CA+U5nMJHAd1TPzZLuhnordBZB8FAy4HBE5PxzfpysU+fTkN2hA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 10 June 2012 19:47, Joshua Berkus <josh(at)agliodbs(dot)com> 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.
The "major limitation" was solved by repmgr close to 2 years ago now.
So while you're correct that the patch to fix that assumed that
archiving worked as well, it has been possible to operate happily
without it.
New versions for 9.2 will be out soon.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2012-06-16 00:09:36 | Re: libpq compression |
Previous Message | Tom Lane | 2012-06-15 22:37:49 | Re: libpq compression |