Re: Logger process and "LOG: could not close client or listen socket: Bad file descriptor"

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Subject: Re: Logger process and "LOG: could not close client or listen socket: Bad file descriptor"
Date: 2023-08-29 03:18:22
Message-ID: CAH2-WzmAJT6MOcm4FMm-eqfhnHr0EKt952bz5fjZ=CuojAHgDw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Aug 27, 2023 at 5:52 PM Michael Paquier <michael(at)paquier(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message John Naylor 2023-08-29 03:26:27 Re: Debian 12 gcc warning
Previous Message Noah Misch 2023-08-29 01:48:19 Re: Query execution in Perl TAP tests needs work