Actually, I think it had more to do with the ambiguities around recovery_target_action, which are documented elsewhere.
On Thu, Mar 4, 2021 at 6:12 AM Laurenz Albe <laurenz.a...@cybertec.at> wrote: > On Wed, 2021-03-03 at 16:58 +0000, PG Doc comments form wrote: > > Under the steps of Recovering with continuous logging, Step 8 says: > > "Start the server. The server will go into recovery mode and proceed to > read > > through the archived WAL files it needs. Should the recovery be > terminated > > because of an external error, the server can simply be restarted and it > will > > continue recovery. Upon completion of the recovery process, the server > will > > remove recovery.signal (to prevent accidentally re-entering recovery mode > > later) and then commence normal database operations." > > > > The server went into recovery mode as expected. However, at the > completion > > of the recovery process, the server did *NOT* remove recovery.signal. Nor > > did the server commend normal database operations. I manually shut down > the > > server, then removed recovery.signal and restarted the server, but then > the > > server recover _past_ my recovery_target_time. I am not sure why. > > The log messages should tell you what is going on. > > Perhaps you used a wrong time zone. > > Yours, > Laurenz Albe > > -- Charles Schultz
