From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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-04 22:48:37 |
Message-ID: | CAMkU=1wo9+TvTy-w9UkSEgwc49kXuu=V=8cEdyaH8CBFyUVeww@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
On Sun, Dec 2, 2012 at 1:02 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Jeff Janes <jeff(dot)janes(at)gmail(dot)com> writes:
>> On Sat, Dec 1, 2012 at 1:56 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> 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.
>
>> No, I'm saying the problem exists both in 9.1.x and in hypothetical
>> 9.2.2 and in hypothetical 9.3, but not in 9.2.[01] because in those it
>> is masked by that other problem which has just been fixed.
>
> I'm still confused. I've now tried this in both HEAD and 9.1 branch
> tip, and I do not see any misbehavior. If I set recovery_target_time to
> before the pg_stop_backup time, I get "FATAL: requested recovery stop
> point is before consistent recovery point" which is what I expect; and
> if I set it to after the pg_stop_backup time, it starts up as expected.
> So if there's a remaining unfixed bug here, I don't understand what
> that is.
I've reproduced it again using the just-tagged 9.2.2, and uploaded a
135MB tarball of the /tmp/data_slave2 and /tmp/archivedir to google
drive. The data directory contains the recovery.conf which is set to
end recovery between the two critical time points.
https://docs.google.com/open?id=0Bzqrh1SO9FcES181YXRVdU5NSlk
This is the command line I use to start recovery, and the resulting log output.
https://docs.google.com/open?id=0Bzqrh1SO9FcEaTQ2QXhFdDZYaUE
I can't connect to the standby to execute pg_xlog_replay_resume() because:
FATAL: the database system is starting up
Cheers,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-12-05 00:20:44 | Re: PITR potentially broken in 9.2 |
Previous Message | Francisco Olarte (M) | 2012-12-04 19:18:31 | Re: BUG #7722: extract(epoch from age(...)) appears to be broken |
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2012-12-04 23:17:41 | Re: Enabling Checksums |
Previous Message | Bruce Momjian | 2012-12-04 22:47:07 | Re: WIP: store additional info in GIN index |