From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
Cc: | 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-01 21:56:44 |
Message-ID: | 16296.1354399004@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
Jeff Janes <jeff(dot)janes(at)gmail(dot)com> writes:
> On Sat, Dec 1, 2012 at 12:47 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Jeff Janes <jeff(dot)janes(at)gmail(dot)com> writes:
>>> In the newly fixed 9_2_STABLE, that problem still shows up the same as
>>> it does in 9.1.6.
>> I tried to reproduce this as per your directions, and see no problem in
>> HEAD. Recovery advances to the specified stop time, hot standby mode
>> wakes up,
> Hot standby should only wake up once recovery has proceeded beyond the
> pg_stop_backup() point.
> If the specified stop point is after pg_start_backup() finishes, but
> before pg_stop_backup(), then hot standby should not start up (and
> with the newest HEAD, in my hands, it does not). Are you sure you set
> the stop time to just after pg_start_backup, not to just after
> pg_stop_backup?
I'm confused. Are you now saying that this problem only exists in
9.1.x? I tested current HEAD because you indicated the problem was
still there.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-12-01 22:56:33 | Re: BUG #7710: Xid epoch is not updated properly during checkpoint |
Previous Message | Jeff Janes | 2012-12-01 21:46:09 | Re: PITR potentially broken in 9.2 |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-12-01 22:24:59 | Re: [PATCH] make -jN check fails / unset MAKEFLAGS in pg_regress.c |
Previous Message | Jeff Janes | 2012-12-01 21:46:09 | Re: PITR potentially broken in 9.2 |