Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tNPCm-00Amwh-8G for pgsql-hackers@arkaria.postgresql.org; Tue, 17 Dec 2024 04:29:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tNPCj-00Ehnh-Hv for pgsql-hackers@arkaria.postgresql.org; Tue, 17 Dec 2024 04:29:06 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tNPCj-00EhnU-7u for pgsql-hackers@lists.postgresql.org; Tue, 17 Dec 2024 04:29:06 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tNPCh-0005US-IE for pgsql-hackers@postgresql.org; Tue, 17 Dec 2024 04:29:05 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 4BH4T11E2159467; Mon, 16 Dec 2024 23:29:01 -0500 From: Tom Lane To: Thomas Munro cc: Alexander Lakhin , pgsql-hackers Subject: Re: Regression tests fail on OpenBSD due to low semmns value In-reply-to: References: Comments: In-reply-to Thomas Munro message dated "Tue, 17 Dec 2024 16:11:37 +1300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2159465.1734409741.1@sss.pgh.pa.us> Date: Mon, 16 Dec 2024 23:29:01 -0500 Message-ID: <2159466.1734409741@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Thomas Munro writes: > Whenever I run into this, or my Mac requires manual ipcrm to clean up > leaked SysV kernel junk, I rebase my patch for sema_kind = 'futex'. > Here it goes. It could be updated to support NetBSD I believe, but I > didn't try as its futex stuff came out later. FWIW, I looked at a nearby NetBSD 10.0 machine. It has /usr/include/sys/futex.h, which includes this enticing comment: /* * Definitions for the __futex(2) synchronization primitive. * * These definitions are intended to be ABI-compatible with the * Linux futex(2) system call. */ However, the complete lack of any user-level documentation makes me misdoubt the extent of their commitment to this :-( I have the same concern about depending on undocumented macOS APIs. Other than that, getting off of SysV semaphores would be a nice thing to do. regards, tom lane