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: Michael Paquier <michael(at)paquier(dot)xyz>
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-14 15:22:55
Message-ID: 23543.1536938575@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:
> Allow concurrent-safe open() and fopen() in frontend code for Windows

I'm surprised you didn't back-patch this --- isn't it a bug fix?

A compromise might be to push it to v11 but not further.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Alvaro Herrera 2018-09-14 15:35:54 Re: pgsql: Improve autovacuum logging for aggressive and anti-wraparound ru
Previous Message Amit Kapila 2018-09-14 04:53:33 pgsql: Don't allow LIMIT/OFFSET clause within sub-selects to be pushed

Browse pgsql-hackers by date

  From Date Subject
Next Message Chris Travers 2018-09-14 15:24:11 Re: Code of Conduct plan
Previous Message Chris Travers 2018-09-14 15:21:59 Re: Code of Conduct plan