Re: BUG #15346: Replica fails to start after the crash

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Alexander Kukushkin <cyberdemn(at)gmail(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15346: Replica fails to start after the crash
Date: 2018-08-22 14:44:40
Message-ID: 20180822144440.vwup4be6l5xuvpk2@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alexander Kukushkin 2018-08-22 15:01:56 Re: BUG #15346: Replica fails to start after the crash
Previous Message Alexander Kukushkin 2018-08-22 14:30:46 Re: BUG #15346: Replica fails to start after the crash

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2018-08-22 14:54:11 Re: JIT compiling with LLVM v12
Previous Message Alvaro Herrera 2018-08-22 14:41:16 Re: patch to allow disable of WAL recycling