Re: BUG #15346: Replica fails to start after the crash - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: BUG #15346: Replica fails to start after the crash
Date
Msg-id 20180822144440.vwup4be6l5xuvpk2@alvherre.pgsql
Whole thread Raw
In response to Re: BUG #15346: Replica fails to start after the crash  (Alexander Kukushkin <cyberdemn@gmail.com>)
Responses Re: BUG #15346: Replica fails to start after the crash  (Alexander Kukushkin <cyberdemn@gmail.com>)
List pgsql-bugs
On 2018-Aug-22, Alexander Kukushkin wrote:

> If I comment out the 'BackgroundWorkerInitializeConnection("postgres",
> NULL);' call, postgres starts without any problem.
> What is very strange, because background worker itself is not doing anything...
> 
> And one more thing, if I add sleep(15) before calling
> BackgroundWorkerInitializeConnection, postgres manages to start
> successfully.
> Is there a very strange race condition here?

Sounds likely.  I suggest to have a look at what's going on inside the
postmaster process when it gets stuck.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-bugs by date:

Previous
From: Alexander Kukushkin
Date:
Subject: Re: BUG #15346: Replica fails to start after the crash
Next
From: Alexander Kukushkin
Date:
Subject: Re: BUG #15346: Replica fails to start after the crash