| From: | Jelte Fennema <Jelte(dot)Fennema(at)microsoft(dot)com> |
|---|---|
| To: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Add ETIMEDOUT to ALL_CONNECTION_FAILURE_ERRNOS |
| Date: | 2021-09-30 10:00:43 |
| Message-ID: | AM5PR83MB01782BFF2978505F6D6C559AF7AA9@AM5PR83MB0178.EURPRD83.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Previously successfully opened TCP connections can still fail on reads
with ETIMEDOUT. This should be considered a connection failure, so that
the connection in libpq is marked as CONNECTION_BAD. The reason I got an
ETIMEDOUT was, because I had set a low tcp_user_timeout in the
connection string. However, it can probably also happen due to
keepalive limits being reached.
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Consider-ETIMEDOUT-a-connection-failure.patch | application/octet-stream | 1010 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Sharma | 2021-09-30 10:07:02 | non-superusers are allowed to drop the replication user, but are not allowed to alter or even create them, is that ok? |
| Previous Message | Drouvot, Bertrand | 2021-09-30 09:52:52 | Re: [BUG] failed assertion in EnsurePortalSnapshotExists() |