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: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Allow concurrent-safe open() and fopen() in frontend code for Wi
Date: 2018-09-18 15:38:57
Message-ID: 25361.1537285137@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> writes:
> Would it be an option to have pgwin32_open default to text mode in
> frontend code and to binary mode in backend code?

Well, the question is why Michael's latest proposed patch doesn't
accomplish that.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Laurenz Albe 2018-09-18 16:04:58 Re: pgsql: Allow concurrent-safe open() and fopen() in frontend code for Wi
Previous Message Laurenz Albe 2018-09-18 15:28:53 Re: pgsql: Allow concurrent-safe open() and fopen() in frontend code for Wi

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2018-09-18 15:45:36 Re: Online verification of checksums
Previous Message Tom Lane 2018-09-18 15:33:38 Re: [HACKERS] proposal - Default namespaces for XPath expressions (PostgreSQL 11)