| 类型: | integer |
| 默认: | 60000 (1min) |
| 最低限度: | 0 (0ms) |
| 最大: | 2147483647 (2147483647ms) |
| 单元: | milliseconds (ms) |
| 上下文: | user |
| 重新开始: | false |
| 以来: | 9.3 |
中断那些停止活动超过这个时间量的复制连接。这对发送服务器检测一个费用服务器崩溃或网络中断有用。 如果指定值时没有单位，则以毫秒为单位。默认值是 60 秒。值0将禁用超时机制。
对于跨越多个地理位置分布的集群，每个位置使用不同的值可以为集群管理带来更大的灵活性。 对于具有低延迟网络连接的备用服务器，较小的值有助于更快的故障检测; 对于位于远端位置的具有高延迟网络连接的备用服务器，较大的值有助于更好地判断备用服务器的健康状况。
在 StackOverflow
- 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
- Getting Exception : "replication slot "XXX" is active for PID XXX`" on deploying service on kubernetes with RollingUpdate deployment strategy
- postgresql 9.4 streaming replication
- What causes data on a read-replica to be an old_snapshot and cause conflict?
在 pgsql-hackers
- outdated references to replication timeout
- RE: Add client connection check during the execution of the query
- Re: pgstat_report_activity() and parallel CREATE INDEX (was: Parallel index creation & pg_stat_activity)
- Recent eelpout failures on 9.x branches
- Re: Logical Replication - behavior of ALTER PUBLICATION .. DROP TABLE and ALTER SUBSCRIPTION .. REFRESH PUBLICATION