0

I have an issue with our logical replication which is still on catchup state. It would read several lsn then got stuck on a particular lsn (EA/738D4DA8 both on sent_lsn and write_lsn) then reset again. I read on the logs and found that it has a written log 'terminating walsender process due to replication timeout' How can i resolve this issue? I'm using Postgresql 12 under Windows Server 2019

Improve this question
2
  • 1
    Well, obvious: increase wal_sender_timeout on the primary.
    – Laurenz Albe
    Commented Nov 1, 2023 at 17:00
  • Thanks @LaurenzAlbe I increased the sender time out (i also adjust the receiver timeout as well) and now the state changes to streaming
    – starting dba jr
    Commented Nov 2, 2023 at 21:18

1 Answer 1

Reset to default
0

If your WAL sender times out, the usual solution is to increase wal_sender_timeout on the sending server. You can set the parameter to 0 to disable the timeout mechanism at all.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.