Re: Direct I/O

Andres Freund <andres@anarazel.de>

From: Andres Freund <andres@anarazel.de>

To: Thomas Munro <thomas.munro@gmail.com>, Heikki Linnakangas <hlinnaka@iki.fi>, Noah Misch <noah@leadboat.com>

Cc: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>, Justin Pryzby <pryzby@telsasoft.com>, pgsql-hackers@postgresql.org

Date: 2023-04-08T18:55:25Z

Lists: pgsql-hackers

Hi,

Given the frequency of failures on this in the buildfarm, I propose using the
temporary workaround of using wal_level=replica. That avoids the use of the
over-eager log_newpage_range().

Greetings,

Andres Freund

Commits

Rename hook functions for debug_io_direct to match variable name.
- 155c81463c26 16.0 landed
- 4f3514f201cf 17.0 landed
Rename io_direct to debug_io_direct.
- 319bae9a8da6 16.0 landed
Skip the 004_io_direct.pl test if a pre-flight check fails.
- 6ca8df2d6147 16.0 landed
Use higher wal_level for 004_io_direct.pl.
- 980e8879f54a 16.0 landed
Skip \password TAP test on old IPC::Run versions
- 2e57ffe12f6b 16.0 cited
Add io_direct setting (developer-only).
- d4e71df6d757 16.0 landed
Introduce PG_IO_ALIGN_SIZE and align all I/O buffers.
- faeedbcefd40 16.0 landed
Add palloc_aligned() to allow aligned memory allocations
- 439f61757f05 16.0 cited
initdb: When running CREATE DATABASE, use STRATEGY = WAL_COPY.
- ad43a413c4f7 15.0 cited