Postgres Pro
Downloads
Home   >   mailing lists

Re: Confusing recovery message when target not hit - Mailing list pgsql-hackers

From Thom Brown
Subject Re: Confusing recovery message when target not hit
Date
Msg-id CAA-aLv4QyTzsaT6RpLvZp0N4yUVMx3X=UU0LNdv136PRXVDvNg@mail.gmail.com
Whole thread Raw
In response to Re: Confusing recovery message when target not hit  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: Confusing recovery message when target not hit
List pgsql-hackers
Tree view
On 12 June 2016 at 12:51, Michael Paquier <michael.paquier@gmail.com> wrote:
On Sun, Jun 12, 2016 at 7:52 PM, Thom Brown <thom@linux.com> wrote:
> Aren't those already set by recoveryStopsBefore()?

It is possible to exit the main redo loop if a NULL record is found
after calling ReadRecord, in which case those would not be set, no?

I'm apprehensive about initialising those values myself as I don't want to set them at a point where they may potentially already be set.

And I've noticed that I didn't re-read my own output messages, so I've corrected them in the attached patch.

Thom
Attachment

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: [PERFORM] 9.4 -> 9.5 regression with queries through pgbouncer on RHEL 6
Next
From: Robert Haas
Date:
Subject: Re: Rename max_parallel_degree?