Re: [HACKERS] Double invocation of InitPostmasterChild in bgworker with -DEXEC_BACKEND

2016-08-04 Thread Robert Haas
On Tue, Aug 2, 2016 at 6:40 PM, Tom Lane wrote: > Thomas Munro 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",

Re: [HACKERS] Double invocation of InitPostmasterChild in bgworker with -DEXEC_BACKEND

2016-08-02 Thread Tom Lane
Thomas Munro 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 cal

[HACKERS] Double invocation of InitPostmasterChild in bgworker with -DEXEC_BACKEND

2016-07-28 Thread Thomas Munro
Hi 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 successful