Hi Tom,
Thanks for the reply.
On the source DB,
we're seeing these messages coming up often, but there aren't any other errors showing up.
All DB parameters including timeout we set to high, but no luck yet.
Pls advise on this
user=replicator DEBUG: failed to increase restart lsn: proposed 13EB/B420DE18, after 13EB/B420DE18, current candidate 13EB/B420DD70, current after 13EB/B420DD70, flushed up to 13EB/B420DBB0
All DB parameters including timeout we set to high, but no luck yet.
Pls advise on this
user=replicator DEBUG: failed to increase restart lsn: proposed 13EB/B420DE18, after 13EB/B420DE18, current candidate 13EB/B420DD70, current after 13EB/B420DD70, flushed up to 13EB/B420DBB0
Thanks & Regards,
Rijesh
On Mon, Dec 9, 2024 at 9:52 PM Tom Lane <tgl@xxxxxxxxxxxxx> wrote:
Rijesh TP <rijesh.tp@xxxxxxxxxxx> writes:
> We are encountering an issue with logical replication on PostgreSQL version
> 15.10. The error message is as follows:
> *"ERROR: could not receive data from WAL stream: SSL SYSCALL error: EOF
> detectedLOG: background worker "logical replication worker" (PID 3286)
> exited with exit code 1."*
This seems to be a symptom of something going wrong on the sending
side. Have you looked into that postmaster's log file to see what
happened?
regards, tom lane
