Hello.
At Mon, 4 May 2020 09:09:15 -0500, Justin King wrote in
> Would there be anyone that might be able to help troubleshoot this
> issue -- or at least give me something that would be helpful to look
> for?
>
> https://www.postgresql.org/message-id/flat/CAGH8ccdWLLGC7qag5pDUFbh96LbyzN_toORh2
Would there be anyone that might be able to help troubleshoot this
issue -- or at least give me something that would be helpful to look
for?
https://www.postgresql.org/message-id/flat/CAGH8ccdWLLGC7qag5pDUFbh96LbyzN_toORh2eY32-2P1%3Dtifg%40mail.gmail.com
https://www.postgresql.org/message-id/flat/
On Thu, Apr 23, 2020 at 3:06 PM Tom Lane wrote:
>
> Justin King writes:
> > I assume it would be related to the following:
> > LOG: incorrect resource manager data checksum in record at 2D6/C259AB90
> > since the walreceiver terminates just after this - but I'm unclear
> > what precisely this me
Justin King writes:
> I assume it would be related to the following:
> LOG: incorrect resource manager data checksum in record at 2D6/C259AB90
> since the walreceiver terminates just after this - but I'm unclear
> what precisely this means.
What it indicates is corrupt data in the WAL stream. W
I assume it would be related to the following:
LOG: incorrect resource manager data checksum in record at 2D6/C259AB90
since the walreceiver terminates just after this - but I'm unclear
what precisely this means. Without digging into the code, I would
guess that it's unable to verify the checks
On Thu, Apr 23, 2020 at 12:47 PM Tom Lane wrote:
>
> Justin King writes:
> > We've seen unexpected termination of the WAL receiver process. This
> > stops streaming replication, but the replica stays available --
> > restarting the server resumes streaming replication where it left off.
> > We'v
Justin King writes:
> We've seen unexpected termination of the WAL receiver process. This
> stops streaming replication, but the replica stays available --
> restarting the server resumes streaming replication where it left off.
> We've seen this across nearly every recent version of PG, (9.4, 9.
We've seen unexpected termination of the WAL receiver process. This
stops streaming replication, but the replica stays available --
restarting the server resumes streaming replication where it left off.
We've seen this across nearly every recent version of PG, (9.4, 9.5,
11.x, 12.x) -- anything om
