Re: pgsql: Allow concurrent-safe open() and fopen() in frontend code for Wi - Mailing list pgsql-committers

From Tom Lane
Subject Re: pgsql: Allow concurrent-safe open() and fopen() in frontend code for Wi
Date
Msg-id 17194.1537191697@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgsql: Allow concurrent-safe open() and fopen() in frontend codefor Wi  (Michael Paquier <michael@paquier.xyz>)
Responses Re: pgsql: Allow concurrent-safe open() and fopen() in frontend codefor Wi  (Michael Paquier <michael@paquier.xyz>)
List pgsql-committers
Michael Paquier <michael@paquier.xyz> writes:
> OK, REL_11_STABLE has been patched as well, after doing a couple of
> extra tests on Windows.

BTW, I'm a bit concerned by the fact that bowerbird has failed its
last couple of HEAD runs at the pgbench step.  The first such
failure was here:

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=bowerbird&dt=2018-09-15%2014%3A19%3A58

Looking at the set of commits between the prior run and that one,
it's hard to see anything that could have triggered the test failures
other than this patch --- but I also don't see how this patch would've
blown up pgbench without breaking earlier tests.  Ideas?

            regards, tom lane


pgsql-committers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: pgsql: Allow concurrent-safe open() and fopen() in frontend codefor Wi
Next
From: Michael Paquier
Date:
Subject: Re: pgsql: Allow concurrent-safe open() and fopen() in frontend codefor Wi