From: Boyer, Maxime (he/him | il/lui) <Maxime.Boyer@cra-arc.gc.ca>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Subject: RE: BUG #18168: Parallel worker failed to initialize: could not create inherited socket: error code 10106
Date: Wed, 25 Oct 2023 14:44:41 +0000
Message-ID: <794802dcff4b44e393f650efc9311f5a@cra-arc.gc.ca> (raw)
In-Reply-To: <970627.1698243684@sss.pgh.pa.us>
References: <18168-ed449e75cefb972a@postgresql.org>
<970627.1698243684@sss.pgh.pa.us>
> 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.
Yeah, that's what I thought :'D
> I am guessing you saw the impact of some external event, but I don't know what.
Fair enough. This happened the day after reverting to 11, because of the memory error on 14, but I also doubt it's related. I was stopping one of the application node at the time. Maybe a Windows thing, or something related to the firmware updates.
We can leave it there for now then. We might try to fallback to see if it happens again.
Thanks,
Maxime
-----Original Message-----
From: Tom Lane <tgl@sss.pgh.pa.us>
Sent: October 25, 2023 10:21 AM
To: Boyer, Maxime (he/him | il/lui) <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
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
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-bugs@postgresql.org
Cc: Maxime.Boyer@cra-arc.gc.ca, tgl@sss.pgh.pa.us, 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: <794802dcff4b44e393f650efc9311f5a@cra-arc.gc.ca>
* 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