Re: Direct I/O

Thomas Munro <thomas.munro@gmail.com>

From: Thomas Munro <thomas.munro@gmail.com>
To: Mikael Kjellström <mikael.kjellstrom@gmail.com>
Cc: Andres Freund <andres@anarazel.de>, Tom Lane <tgl@sss.pgh.pa.us>, Andrew Dunstan <andrew@dunslane.net>, Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>, Christoph Berg <myon@debian.org>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2023-04-15T00:26:53Z
Lists: pgsql-hackers
On Sat, Apr 15, 2023 at 7:50 AM Mikael Kjellström
<mikael.kjellstrom@gmail.com> wrote:
> want me to switch to clang instead?

I vote +1, that's the system compiler in modern OpenBSD.

https://www.cambus.net/the-state-of-toolchains-in-openbsd/

As for curculio, I don't understand the motivation for maintaining
that machine.  I'd rather know if OpenBSD 7.3 works.



Commits

  1. Rename hook functions for debug_io_direct to match variable name.

  2. Rename io_direct to debug_io_direct.

  3. Skip the 004_io_direct.pl test if a pre-flight check fails.

  4. Use higher wal_level for 004_io_direct.pl.

  5. Skip \password TAP test on old IPC::Run versions

  6. Add io_direct setting (developer-only).

  7. Introduce PG_IO_ALIGN_SIZE and align all I/O buffers.

  8. Add palloc_aligned() to allow aligned memory allocations

  9. initdb: When running CREATE DATABASE, use STRATEGY = WAL_COPY.