| 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-05 17:36:39 |
| Message-ID: | 8223.1354728999@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:
> On 2012-12-05 17:24:42 +0000, Simon Riggs wrote:
>> So ISTM that we should make recoveryStopsHere() return false while we
>> are inconsistent. Problems solved.
> I prefer the previous (fixed) behaviour where we error out if we reach a
> recovery target before we are consistent:
I agree. Silently ignoring the user's specification is not good.
(I'm not totally sure about ignoring the pause spec, either, but
there is no good reason to change the established behavior for
the recovery target spec.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John R Pierce | 2012-12-05 17:46:34 | Re: PostgreSQL v8.1.11 compatibility with OS 2008 R2 |
| Previous Message | Andres Freund | 2012-12-05 17:30:25 | Re: PITR potentially broken in 9.2 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2012-12-05 17:39:35 | Re: Slow query: bitmap scan troubles |
| Previous Message | Andres Freund | 2012-12-05 17:30:25 | Re: PITR potentially broken in 9.2 |