Re: BUG #18168: Parallel worker failed to initialize: could not create inherited socket: error code 10106
От
Tom Lane
Тема
Re: BUG #18168: Parallel worker failed to initialize: could not create inherited socket: error code 10106
Дата
Msg-id
970627.1698243684@sss.pgh.pa.us
Ответ на
BUG #18168: Parallel worker failed to initialize: could not create inherited socket: error code 10106 (PG Bug reporting form)
Список
Дерево обсуждения
BUG #18168: Parallel worker failed to initialize: could not create inherited socket: error code 10106 PG Bug reporting form <noreply@postgresql.org>
Re: BUG #18168: Parallel worker failed to initialize: could not create inherited socket: error code 10106 Tom Lane <tgl@sss.pgh.pa.us>
RE: BUG #18168: Parallel worker failed to initialize: could not create inherited socket: error code 10106 "Boyer, Maxime (he/him | il/lui)" <Maxime.Boyer@cra-arc.gc.ca>
Re: BUG #18168: Parallel worker failed to initialize: could not create inherited socket: error code 10106 Thomas Munro <thomas.munro@gmail.com>
RE: BUG #18168: Parallel worker failed to initialize: could not create inherited socket: error code 10106 "Boyer, Maxime (he/him | il/lui)" <Maxime.Boyer@cra-arc.gc.ca>
PG Bug reporting form 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
В списке pgsql-bugs по дате отправления
От: Tom Lane
Дата:
От: Boyer, Maxime (he/him | il/lui)
Дата: