Re: PITR potentially broken in 9.2

Jeff Janes <jeff(dot)janes(at)gmail(dot)com> writes:
> 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.

Hmmm ... I can reproduce this with current 9.2 branch tip. However,
more or less by accident I first tried it with a 9.2-branch postmaster
from a couple weeks ago, and it works as expected with that: the log
output looks like

LOG: restored log file "00000001000000000000001B" from archive
LOG: restored log file "00000001000000000000001C" from archive
LOG: restored log file "00000001000000000000001D" from archive
LOG: database system is ready to accept read only connections
LOG: recovery stopping before commit of transaction 305610, time 2012-12-02 15:08:54.000131-08
LOG: recovery has paused
HINT: Execute pg_xlog_replay_resume() to continue.

and I can connect and do the pg_xlog_replay_resume() thing.
Note the "ready to accept read only connections" line, which
does not show up with branch tip.

So apparently this is something we broke since Nov 18. Don't know what
yet --- any thoughts? Also, I am still not seeing what the connection
is to the original report against 9.1.6.

regards, tom lane