Re: Direct I/O

Andrew Dunstan <andrew@dunslane.net>

From: Andrew Dunstan <andrew@dunslane.net>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: Andres Freund <andres@anarazel.de>, Tom Lane <tgl@sss.pgh.pa.us>, Heikki Linnakangas <hlinnaka@iki.fi>, Noah Misch <noah@leadboat.com>, Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>, Justin Pryzby <pryzby@telsasoft.com>, pgsql-hackers@postgresql.org
Date: 2023-04-09T11:25:13Z
Lists: pgsql-hackers
On 2023-04-08 Sa 18:50, Thomas Munro wrote:
> On Sun, Apr 9, 2023 at 10:17 AM Andrew Dunstan<andrew@dunslane.net>  wrote:
>> I can run the test in isolation, and it's get an error reliably.
> Random idea: it looks like you have compression enabled.  What if you
> turn it off in the directory where the test runs?  Something like
> btrfs property set <file> compression ... according to the
> intergoogles.  (I have never used btrfs before 6 minutes ago but I
> can't seem to repro this with basic settings in a loopback btrfs
> filesystems).


Didn't seem to make any difference.


cheers


andrew

--
Andrew Dunstan
EDB:https://www.enterprisedb.com

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.