> 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
firmwareupdates.
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
