| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | pgsql-committers(at)lists(dot)postgresql(dot)org, Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Subject: | Re: pgsql: Allow concurrent-safe open() and fopen() in frontend code for Wi |
| Date: | 2018-09-17 13:41:37 |
| Message-ID: | 17194.1537191697@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Michael Paquier <michael(at)paquier(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2018-09-17 14:02:02 | Re: pgsql: Allow concurrent-safe open() and fopen() in frontend code for Wi |
| Previous Message | Michael Paquier | 2018-09-17 11:49:30 | Re: pgsql: Improve autovacuum logging for aggressive and anti-wraparound ru |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2018-09-17 14:02:02 | Re: pgsql: Allow concurrent-safe open() and fopen() in frontend code for Wi |
| Previous Message | Chris Travers | 2018-09-17 13:28:02 | Strange OSX make check-world failure |