On Fri, Nov 7, 2025 at 2:35 PM Bryan Green wrote:
> If you agree, and I think you do, I will implement the SOCK_CLOEXEC
> abstraction and the socket_set_cloexec helper for this. My bug fix will
> be the first user.
+1
Thanks for working on all this stuff.
> I also need to handle the handles fo
On 11/6/25 19:03, Thomas Munro wrote:
On Fri, Nov 7, 2025 at 7:53 AM Bryan Green wrote:
The socket fix adds WSA_FLAG_NO_HANDLE_INHERIT to WSASocket() in
pgwin32_socket(), and calls SetHandleInformation() in
BackendInitialize() to mark the inherited client socket non-inheritable.
The latter is n
On Fri, Nov 7, 2025 at 7:53 AM Bryan Green wrote:
> > The socket fix adds WSA_FLAG_NO_HANDLE_INHERIT to WSASocket() in
> > pgwin32_socket(), and calls SetHandleInformation() in
> > BackendInitialize() to mark the inherited client socket non-inheritable.
> > The latter is needed because handles pas
shared memory will follow over the next couple of
> days.
>
Incorrect extension on the patch. Attached is the correct patch.
--
Bryan Green
EDB: https://www.enterprisedb.comFrom 1eb87b403b67dbb3e7d59c8c82cd3d274d2372de Mon Sep 17 00:00:00 2001
From: Bryan Green
Date: Wed, 5 Nov 2025 22:24:35 -0600
Subject: [PATCH] Fi
and shared memory will follow over the next couple of
days.
--
Bryan Green
EDB: https://www.enterprisedb.com
From 1eb87b403b67dbb3e7d59c8c82cd3d274d2372de Mon Sep 17 00:00:00 2001
From: Bryan Green
Date: Wed, 5 Nov 2025 22:24:35 -0600
Subject: [PATCH] Fix socket handle inheritance on Windows
