Re: BUG #16526: pg_test_fsync in v12 doesn't run in Windows - Mailing list pgsql-bugs

From Michael Paquier
Subject Re: BUG #16526: pg_test_fsync in v12 doesn't run in Windows
Date
Msg-id 20200714035458.GD10826@paquier.xyz
Whole thread Raw
In response to Re: BUG #16526: pg_test_fsync in v12 doesn't run in Windows  (Bruce Momjian <bruce@momjian.us>)
Responses Re: BUG #16526: pg_test_fsync in v12 doesn't run in Windows
List pgsql-bugs
On Mon, Jul 13, 2020 at 08:06:25PM -0400, Bruce Momjian wrote:
> Well, pg_test_fsync is testing binary writes, so using TEXT for the
> files might add unwanted overhead, so I think binary is the best
> approach.

Thanks.  Please note that we have switched frontend tools to use our
concurrent-safe flavor of open() and fopen() as of 0ba06e0 (12 and
newer versions), but 40cfe86 has shown that we have been using the
text mode in pg_test_fsync since forever as Windows' open() uses the
text mode by default if we don't specify _fmode with _setmode():
https://docs.microsoft.com/en-us/cpp/c-runtime-library/fmode?view=vs-2019

For this reason, it seems more sensible to me to not backpatch this
change only down to 12, but actually all the way down to 9.5.
--
Michael

Attachment

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Small query using LATERAL that segfaults Postgres
Next
From: PG Bug reporting form
Date:
Subject: BUG #16539: About pg_logdir_ls() function and pg_ls_logdir()function