| Type: | integer |
| Default: | 0 (0ms) |
| Min: | 0 (0ms) |
| Max: | 2147483647 (2147483647ms) |
| Unit: | milliseconds (ms) |
| Context: | user |
| Restart: | false |
| Since: | 12 |
Specifies the amount of time that transmitted data may remain unacknowledged before the TCP connection is forcibly closed. If this value is specified without units, it is taken as milliseconds. A value of 0 (the default) selects the operating system's default. This parameter is supported only on systems that support TCP_USER_TIMEOUT; on other systems, it must be zero. In sessions connected via a Unix-domain socket, this parameter is ignored and always reads as zero.
This parameter is not supported on Windows, and must be zero.
On StackOverflow
- pgadmin4 unable to connect to server,FATAL: password authentication failed for user "postgres"
- Postgres was not running when connecting to a server
- PostgreSQL 13 sometimes works but sometimes huge execution time
- Java Hibernate insert hypertable in timescaledb is very slow
- Why does "explain analyzing" this query fnish fast (showing a parallel plan), while running the actual query without "explain analyze" doesn't?
On pgsql-hackers
- Re: [EXTERNAL] Re: Add ETIMEDOUT to ALL_CONNECTION_FAILURE_ERRNOS
- Re: PQcancel does not use tcp_user_timeout, connect_timeout and keepalive settings
- Add ETIMEDOUT to ALL_CONNECTION_FAILURE_ERRNOS
- PQcancel does not use tcp_user_timeout, connect_timeout and keepalive settings
- Re: Add ETIMEDOUT to ALL_CONNECTION_FAILURE_ERRNOS