Postgres Pro
Downloads
Home   >   mailing lists

Re: Logger process and "LOG: could not close client or listen socket: Bad file descriptor" - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Logger process and "LOG: could not close client or listen socket: Bad file descriptor"
Date
Msg-id CAH2-WzmAJT6MOcm4FMm-eqfhnHr0EKt952bz5fjZ=CuojAHgDw@mail.gmail.com
Whole thread Raw
In response to Logger process and "LOG: could not close client or listen socket: Bad file descriptor"  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Logger process and "LOG: could not close client or listen socket: Bad file descriptor"
List pgsql-hackers
Tree view 
On Sun, Aug 27, 2023 at 5:52 PM Michael Paquier <michael@paquier.xyz> wrote:
> From what I can see, this is is a rather old issue, because
> ListenSocket[] is filled with PGINVALID_SOCKET *after* starting the
> syslogger.  It seems to me that we should just initialize the array
> before starting the syslogger, so as we don't get these incorrect
> logs?
>
> Thoughts?  Please see the attached.

Agreed, this is very annoying. I'm going to start using your patch
with the feature branch I'm working on. Hopefully that won't be
necessary for too much longer.


--
Peter Geoghegan

pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: Query execution in Perl TAP tests needs work
Next
From: John Naylor
Date:
Subject: Re: Debian 12 gcc warning