Terminate replication connections that are inactive for longer than this amount of time. This is useful for the sending server to detect a standby crash or network outage. If this value is specified without units, it is taken as milliseconds. The default value is 60 seconds. A value of zero disables the timeout mechanism.
With a cluster distributed across multiple geographic locations, using different values per location brings more flexibility in the cluster management. A smaller value is useful for faster failure detection with a standby having a low-latency network connection, and a larger value helps in judging better the health of a standby if located on a remote location, with a high-latency network connection.
- PostgreSQL logical replication stacks with error 'could not receive data from WAL stream: server closed the connection unexpectedly'
- how to resolve ERROR: could not start WAL streaming: ERROR: replication slot "xxx" is active for PID 124563
- postgresql 9.4 streaming replication
- What causes data on a read-replica to be an old_snapshot and cause conflict?
- Out of space due to wal files
- [PATCH] Race condition in logical walsender causes long postgresql shutdown delay
- Re: Non working timeout detection in logical worker
- pg_basebackup is taking an unusually long time with Postgres 11.3
- Re: pg_receivewal documentation
- Re: Primary keepalive message not appearing in Logical Streaming Replication