Re: Replace open mode with PG_BINARY_R/W/A macros

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
Cc: Japin Li <japinli(at)hotmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Replace open mode with PG_BINARY_R/W/A macros
Date: 2022-04-21 20:38:19
Message-ID: 3478326.1650573499@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> writes:
> On 20.04.22 22:29, Tom Lane wrote:
>> PG_BINARY is useful for open(). It's the PG_BINARY_R/W/A macros for
>> fopen() that are redundant per POSIX. Possibly someone generalized
>> inappropriately; or maybe long ago we supported some platform that
>> rejected the "b" option?

> I think the latter was the case. I doubt it's still a problem.

We could find that out with little effort, at least for machines in the
buildfarm, by modifying c.h to use the form with "b" always.

> I see some of the new code in pg_basebackup uses "wb" directly. It
> would probably be good to fix that to be consistent one way or the
> other. I vote for getting rid of the macros.

Yeah, I suspect there have been other inconsistencies for years :-(

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2022-04-21 20:45:16 Re: Assert failure in CTE inlining with view and correlated subquery
Previous Message Peter Eisentraut 2022-04-21 20:36:01 Re: [RFC] building postgres with meson -v8