From: Tom Lane <tgl@sss.pgh.pa.us>
To: maxime.boyer@cra-arc.gc.ca
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18168: Parallel worker failed to initialize: could not
 create inherited socket: error code 10106
In-reply-to: <18168-ed449e75cefb972a@postgresql.org>
References: <18168-ed449e75cefb972a@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Tue, 24 Oct 2023 19:40:41 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <970626.1698243684.1@sss.pgh.pa.us>
Date: Wed, 25 Oct 2023 10:21:24 -0400
Message-ID: <970627.1698243684@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/970627.1698243684%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> New firmware were installed on the server, this happened after restarting
> the server. Since then, the database runs on a secondary server without
> issue. That server received the same updates. We haven't tried moving it
> back as this is our production database. Was this a fluke?

> 83 identical errors were logged in the system Event Viewer:
> could not create inherited socket: error code 10106

FWIW, the PG code that throws that error message is old enough
to vote; it's not something we changed in a recent minor release.
So I doubt the PG upgrade was the triggering factor.

I am guessing you saw the impact of some external event,
but I don't know what.

			regards, tom lane