Horton

Re: Direct I/O

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

View thread View on postgr.es
From: Mikael Kjellström <mikael.kjellstrom@mksoft.nu>
To: Tom Lane <tgl@sss.pgh.pa.us>, Thomas Munro <thomas.munro@gmail.com>
Cc: Andres Freund <andres@anarazel.de>, Andrew Dunstan <andrew@dunslane.net>, 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-16T07:54:15Z
Lists: pgsql-hackers 

On 2023-04-16 00:10, Tom Lane wrote:

> so curculio should be the only one that's at risk here.
> Maybe just upgrading it is the right answer.

Just let me know if I should switch curculio to OpenBSD 7.3.

I already have a new server setup so only need to switch the "animal" 
and "secret" and enable the cron job to get it running.

/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.