pgsql: Close socket in case of errors in setting non-blocking

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:32:11
Message-ID: E1rQ3DP-001pX9-T5@gemulon.postgresql.org
Views: Raw Message | Whole Thread | 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
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/7cfa154d15c4a98bea0cfe26b2c78094a094650f

Modified Files
--------------
src/backend/port/win32/socket.c | 1 +
1 file changed, 1 insertion(+)

Browse pgsql-committers by date

  From Date Subject
Next Message Daniel Gustafsson 2024-01-17 10:33:52 pgsql: Close socket in case of errors in setting non-blocking
Previous Message Michael Paquier 2024-01-17 08:03:42 pgsql: Fix description of DecodeInsert() in decode.c