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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: 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 11:41:13
Message-ID: 20180917114113.GA31460@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Sat, Sep 15, 2018 at 07:49:39AM +0900, Michael Paquier wrote:
> I would be fine to get that into v11 though, as that is not released
> yet. You will have to wait for a couple of days though, there is a long
> week-end here away from laptops and electronic devices ;)

OK, REL_11_STABLE has been patched as well, after doing a couple of
extra tests on Windows.
--
Michael

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2018-09-17 11:49:30 Re: pgsql: Improve autovacuum logging for aggressive and anti-wraparound ru
Previous Message Michael Paquier 2018-09-17 11:39:21 pgsql: Allow concurrent-safe open() and fopen() in frontend code for Wi

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2018-09-17 11:49:30 Re: pgsql: Improve autovacuum logging for aggressive and anti-wraparound ru
Previous Message David Rowley 2018-09-17 11:21:49 Re: Tid scan improvements