| From: | Daniel Gustafsson <dgustafsson(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Close socket in case of errors in setting non-blocking |
| Date: | 2024-01-17 10:35:32 |
| Message-ID: | E1rQ3Ge-001pb7-I1@gemulon.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Close socket in case of errors in setting non-blocking
If configuring the newly created socket non-blocking fails we
error out and return INVALID_SOCKET, but the socket that had
been created wasn't closed. Fix by issuing closesocket in the
errorpath.
Backpatch to all supported branches.
Author: Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>
Discussion: https://postgr.es/m/CAEudQApmU5CrKefH85VbNYE2y8H=-qqEJbg6RAPU65+vCe+89A@mail.gmail.com
Backpatch-through: v12
Branch
------
REL_12_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/db0d238419decf7edfd84b24d1a151b3ac21dc6a
Modified Files
--------------
src/backend/port/win32/socket.c | 1 +
1 file changed, 1 insertion(+)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2024-01-17 13:57:36 | pgsql: Fix incorrect comment on how BackendStatusArray is indexed |
| Previous Message | Daniel Gustafsson | 2024-01-17 10:35:27 | pgsql: Close socket in case of errors in setting non-blocking |