Re: Double invocation of InitPostmasterChild in bgworker with -DEXEC_BACKEND - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Double invocation of InitPostmasterChild in bgworker with -DEXEC_BACKEND
Date
Msg-id 10230.1470177637@sss.pgh.pa.us
Whole thread Raw
In response to Double invocation of InitPostmasterChild in bgworker with -DEXEC_BACKEND  (Thomas Munro <thomas.munro@enterprisedb.com>)
Responses Re: Double invocation of InitPostmasterChild in bgworker with -DEXEC_BACKEND  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Thomas Munro <thomas.munro@enterprisedb.com> writes:
> I discovered that if you build with -DEXEC_BACKEND on a Unix system
> and then try to start a background worker, it dies in
> InitializeLatchSupport:

> TRAP: FailedAssertion("!(selfpipe_readfd == -1)", File: "latch.c", Line: 161)

> That's because InitPostmasterChild is called twice.  I can
> successfully use regular parallel query workers and bgworkers created
> by extensions if I apply the attached patch.

Confirmed, fix pushed.  I wonder if we should have a buildfarm member
running the Unix EXEC_BACKEND code ...
        regards, tom lane



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Increasing timeout of poll_query_until for TAP tests
Next
From: Tom Lane
Date:
Subject: Re: Changed SRF in targetlist handling