Re: Misleading "epoll_create1 failed: Too many open files" - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Misleading "epoll_create1 failed: Too many open files"
Date
Msg-id 1682220.1732638956@sss.pgh.pa.us
Whole thread Raw
In response to Misleading "epoll_create1 failed: Too many open files"  (Andres Freund <andres@anarazel.de>)
Responses Re: Misleading "epoll_create1 failed: Too many open files"
List pgsql-hackers
Andres Freund <andres@anarazel.de> writes:
> I think it's rather confusing to claim that epoll_create1() failed when we
> didn't even call it.
> Why are we misattributing the failure to a system call that we didn't make?

I think the idea was that this mechanism is equivalent to an EMFILE
limit.  But if you feel a need to make a distinction, this seems fine:

>                 elog(ERROR, "AcquireExternalFD, for epoll_create1, failed: %m");

You should probably check all of 3d475515a, because I think
I applied the same idea in more than one place.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: What db objects can only be created with superuser?
Next
From: Bruce Momjian
Date:
Subject: Re: Doc: typo in config.sgml