| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | maxime(dot)boyer(at)cra-arc(dot)gc(dot)ca |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18168: Parallel worker failed to initialize: could not create inherited socket: error code 10106 |
| Date: | 2023-10-25 14:21:24 |
| Message-ID: | 970627.1698243684@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
PG Bug reporting form <noreply(at)postgresql(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Boyer, Maxime (he/him | il/lui) | 2023-10-25 14:44:41 | RE: BUG #18168: Parallel worker failed to initialize: could not create inherited socket: error code 10106 |
| Previous Message | Tom Lane | 2023-10-25 13:51:31 | Re: AW: AW: BUG #18147: ERROR: invalid perminfoindex 0 in RTE with relid xxxxx |