From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Request for vote to move forward with recovery.conf overhaul |
Date: | 2012-12-22 00:49:42 |
Message-ID: | CA+U5nM+r-vBXBrBhhwCKiM4Mm9cvW-Ebvbf7V5Uc-FtLhM8f_Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 21 December 2012 19:46, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> There has been discussion in the past of removing or significantly
> changing the way streaming replication/point-in-time-recovery (PITR) is
> setup in Postgres. Currently the file recovery.conf is used, but that
> was designed for PITR and does not serve streaming replication well.
>
> This all should have been overhauled when streaming replication was
> added in 2010 in Postgres 9.0. However, time constraints and concern
> about backward compatibility has hampered this overhaul.
>
> 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.
Given that I've said all along that I want change, I'll vote for that,
especially since it is so reasonably worded.
I also want backwards compatibility, so I would like whoever does this
change to also spend some time on that, since it seems that the
balance of time/cost is good enough to make it sensible to do so. I
hope we can spend the time on that investigation, rather than further
debate around what we mean by the word minimally.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2012-12-22 00:57:47 | Re: Review of Row Level Security |
Previous Message | Simon Riggs | 2012-12-22 00:42:43 | Re: Commits 8de72b and 5457a1 (COPY FREEZE) |