Quick Links

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

From:	Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To:	Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>
Cc:	Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject:	Re: pgsql: Allow concurrent-safe open() and fopen() in frontend code for Wi
Date:	2018-09-17 22:00:58
Message-ID:	28249.1537221658@sss.pgh.pa.us
Views:	Raw Message \| Whole Thread \| Download mbox \| Resend email
Thread:
Lists:	pgsql-committers pgsql-hackers

Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> writes:
> On 09/17/2018 12:13 PM, Tom Lane wrote:
>> Pushed, please test.

> Tests are still running, but it's past the pgbench stage on HEAD, so I
> think we're good.

I was more concerned about whether any of the post-pgbench steps would
show a failure; but it looks like HEAD's green, so probably v11 is too.

regards, tom lane

	From	Date	Subject
Next Message	Tom Lane	2018-09-17 22:44:24	pgsql: Stamp 11beta4.
Previous Message	Andrew Dunstan	2018-09-17 18:30:40	Re: pgsql: Allow concurrent-safe open() and fopen() in frontend code for Wi

	From	Date	Subject
Next Message	Stephen Frost	2018-09-17 22:01:33	Re: Online verification of checksums
Previous Message	Tom Lane	2018-09-17 21:50:15	Re: Query is over 2x slower with jit=on