| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, Pg Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: PITR potentially broken in 9.2 |
| Date: | 2012-12-06 00:37:55 |
| Message-ID: | 18896.1354754275@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> What I dislike with what you committed is that the state you're
> investigating during the pause isn't the one youre going to end up
> recoveryApply == true. That seems dangerous to me, even if its going to
> be reworked in HEAD.
Agreed, but it's been like that since the pause feature was created, and
we've not heard complaints (which TBH makes me wonder how much use the
feature has actually seen). I'm hesitant to change the semantics in the
back branches more than necessary to avoid clear-showstopper cases.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sachin Srivastava | 2012-12-06 05:39:45 | Re: BUG #7728: Trouble installing postgresql for the first time |
| Previous Message | Jeff Janes | 2012-12-06 00:35:00 | Re: PITR potentially broken in 9.2 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-12-06 00:43:08 | Re: Commits 8de72b and 5457a1 (COPY FREEZE) |
| Previous Message | Jeff Janes | 2012-12-06 00:35:00 | Re: PITR potentially broken in 9.2 |