Re: BUG #16526: pg_test_fsync in v12 doesn't run in Windows

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: jeff(dot)janes(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16526: pg_test_fsync in v12 doesn't run in Windows
Date: 2020-07-14 03:54:58
Message-ID: 20200714035458.GD10826@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2020-07-14 04:29:48 BUG #16539: About pg_logdir_ls() function and pg_ls_logdir()function
Previous Message Tom Lane 2020-07-14 00:40:38 Re: Small query using LATERAL that segfaults Postgres