pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Andres Freund <andres@anarazel.de>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Distinguish between AcquireExternalFD and epoll_create1 / kqueue
Date: Tue, 26 Nov 2024 17:52:20 +0000
Message-ID: <E1tFzjY-003dr5-02@gemulon.postgresql.org> (raw)

Distinguish between AcquireExternalFD and epoll_create1 / kqueue failing

The error messages in CreateWaitEventSet() made it hard to know whether the
syscall or AcquireExternalFD() failed. This is particularly relevant because
AcquireExternalFD() imposes a lower limit than what would cause syscalls fail
with EMFILE.

I did not change the message in libpqsrv_connect_prepare(), which is the one
other use of AcquireExternalFD() in our codebase, as the error message already
is less ambiguous.

Reviewed-by: Tom Lane <tgl@sss.pgh.pa.us>
Discussion: https://postgr.es/m/xjjx7r4xa7beixuu4qtkdhnwdbchrrpo3gaeb3jsbinvvdiat5@cwjw55mna5of

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/b8f9afc81f26ead612fcfe76301c01d110e36c7e

Modified Files
--------------
src/backend/storage/ipc/latch.c | 10 ++--------
1 file changed, 2 insertions(+), 8 deletions(-)



Message-ID: <E1tFzjY-003dr5-02@gemulon.postgresql.org>
Permalink:  ../E1tFzjY-003dr5-02@gemulon.postgresql.org/
Also on:    postgresql.org/message-id/E1tFzjY-003dr5-02@gemulon.postgresql.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-committers@postgresql.org
  Cc: andres@anarazel.de, pgsql-committers@lists.postgresql.org
  Subject: Re: pgsql: Distinguish between AcquireExternalFD and epoll_create1 / kqueue
  In-Reply-To: <E1tFzjY-003dr5-02@gemulon.postgresql.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox