Horton

Re: Intermittent pg_ctl failures on Windows

Michael Paquier <michael@paquier.xyz>

View thread View on postgr.es
From: Michael Paquier <michael@paquier.xyz>
To: r.zharkov@postgrespro.ru
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Badrul Chowdhury <bachow@microsoft.com>, pgsql-hackers@lists.postgresql.org
Date: 2019-07-18T08:51:48Z
Lists: pgsql-hackers 
On Wed, Jul 17, 2019 at 09:54:16PM +0700, r.zharkov@postgrespro.ru wrote:
> You are right. I tested branch REL_11_STABLE and it is my mistake.
>
> [...]
>
> The probability is very small. In one of our tests pg_ctl fails with that
> error sometime.
> In a test with multiple frequent restarts the probability is 5-6%. On other
> machines probability differs.
> To find out the real error code we used the Process Monitor utility.

I would like to be sure of something here.  Are those failures based
on what you have tested on REL_11_STABLE or do you still see pg_ctl
complain about such things on HEAD (post f02259fe as mentioned by Tom
upthread)?  I would like to think that you mean the former and the
latter, but this thread mentions only the former.
--
Michael

Commits

  1. Allow concurrent-safe open() and fopen() in frontend code for Windows

  2. Change pg_ctl to detect server-ready by watching status in postmaster.pid.