Type: | integer |
Default: | 60000 (1min) |
Min: | 0 (0ms) |
Max: | 2147483647 (2147483647ms) |
Unit: | milliseconds (ms) |
Context: | user |
Restart: | false |
Since: | 9.3 |
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.
On StackOverflow
On pgsql-hackers
- dikkop failed the pg_combinebackupCheck/006_db_file_copy.pl test
- Re: Instability with incremental backup tests (pg_combinebackup, 003_timeline.pl)
- Re: Increase of maintenance_work_mem limit in 64-bit Windows
- Re: Introduce XID age and inactive timeout based replication slot invalidation
- Re: GUC-ify walsender MAX_SEND_SIZE constant