From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Alexander Kukushkin <cyberdemn@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #15346: Replica fails to start after the crash
Date: Wed, 22 Aug 2018 11:44:40 -0300
Message-ID: <20180822144440.vwup4be6l5xuvpk2@alvherre.pgsql> (raw)
In-Reply-To: <CAFh8B=mHh7iLGLLCjicUsJgTkz_2_=WsOpR4KvFOfo2bTX4v2g@mail.gmail.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: alvherre@2ndquadrant.com, cyberdemn@gmail.com, michael@paquier.xyz, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #15346: Replica fails to start after the crash
In-Reply-To: <20180822144440.vwup4be6l5xuvpk2@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox