Re: intermittent test failure on Windows - Mailing list pgsql-hackers

From Tom Lane
Subject Re: intermittent test failure on Windows
Date
Msg-id 3023.1571684293@sss.pgh.pa.us
Whole thread Raw
In response to intermittent test failure on Windows  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
Responses Re: intermittent test failure on Windows
List pgsql-hackers
Andrew Dunstan <andrew.dunstan@2ndquadrant.com> writes:
> Bowerbird (Visual Studio 2017 / Windows 10 pro) just had a failure on
> the pg_ctl test :
> <https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=bowerbird&dt=2019-10-21%2011%3A50%3A21>

> I surmise that what's happening here is that the test is trying to read
> current_logfiles while the server is writing it, so there's a race
> condition.

Hmm ... the server tries to replace current_logfiles atomically
with rename(), so this says that rename isn't atomic on Windows,
which we knew already.  Previous discussion (cf. commit d611175e5)
implies that an even worse failure condition is possible: the server
might fail to rename current_logfiles.tmp into place, just because
somebody is trying to read current_logfiles.  Ugh.

I found a thread about trying to make a really bulletproof rename()
for Windows:

https://www.postgresql.org/message-id/flat/CAPpHfds7dyuGZt%2BPF2GL9qSSVV0OZnjNwqiCPjN7mirDw882tA%40mail.gmail.com

but it looks like we gave up in disgust.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: Proposal: Make use of C99 designated initialisers fornulls/values arrays
Next
From: Tom Lane
Date:
Subject: Re: Proposal: Make use of C99 designated initialisers for nulls/values arrays