| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andres Freund <andres(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-05 17:24:42 |
| Message-ID: | CA+U5nMKKY4NTJa+i5OJYs2Mh8i=B3249A3ji=L0-hr4c1G7qMw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On 5 December 2012 17:17, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> The recovery target and the consistency point are in some ways in
> conflict. If the recovery target is before the consistency point there
> is no point in stopping there, whether or not we pause. What we should
> do is say "recovery target reached, yet recovery not yet consistent,
> continuing".
> So ISTM that we should make recoveryStopsHere() return false while we
> are inconsistent. Problems solved.
Patch
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| recovery_dont_stop_when_inconsistent.v1.patch | application/octet-stream | 538 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2012-12-05 17:30:25 | Re: PITR potentially broken in 9.2 |
| Previous Message | Simon Riggs | 2012-12-05 17:17:20 | Re: PITR potentially broken in 9.2 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2012-12-05 17:27:47 | Re: Dumping an Extension's Script |
| Previous Message | Andrew Dunstan | 2012-12-05 17:22:46 | Re: json accessors |