Re: Direct I/O

Mikael Kjellström <mikael.kjellstrom@mksoft.nu>

From: Mikael Kjellström <mikael.kjellstrom@mksoft.nu>
To: Andrew Dunstan <andrew@dunslane.net>, Tom Lane <tgl@sss.pgh.pa.us>
Cc: Thomas Munro <thomas.munro@gmail.com>, Andres Freund <andres@anarazel.de>, Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>, Christoph Berg <myon@debian.org>, mikael.kjellstrom@gmail.com, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2023-04-17T05:44:36Z
Lists: pgsql-hackers

On 2023-04-16 20:05, Mikael Kjellström wrote:

>>> Oh wait ... this involves a switch from gcc in OpenBSD 5.9 to clang
>>> in OpenBSD 7.3, doesn't it?  That isn't something update_personality
>>> will handle; you need a new animal if the compiler product is changing.
>>>
>>
>> Correct.
> 
> OK. I registered a new animal for this then.
> 
> So if someone could look at that and give be an animal name + secret I 
> can set this up.

I have setup a new animal "schnauzer" (thanks andrew!).

That should report in a little while.

/Mikael




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.