Re: Direct I/O

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>, Christoph Berg <myon(at)debian(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Direct I/O
Date: 2023-04-13 02:04:59
Message-ID: CA+hUKGJFXVsFPZkU1uqWUHY-amWB974oJ2D85VGG3aGp3xURNA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thanks both for looking, and thanks for the explanation Ilmari.
Pushed with your improvements. The 4 CI systems run the tests
(Windows and Mac by special always-expected-to-work case, Linux and
FreeBSD by successful pre-flight perl test of O_DIRECT), and I also
tested three unusual systems, two that skip for different reasons and
one that will henceforth run this test on the build farm so I wanted
to confirm locally first:

Linux/tmpfs: 1..0 # SKIP pre-flight test if we can open a file with
O_DIRECT failed: Invalid argument
OpenBSD: t/004_io_direct.pl .............. skipped: no O_DIRECT
illumos: t/004_io_direct.pl .............. ok

(Format different because those last two are autoconf, no meson on my
collection of Vagrant images yet...)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2023-04-13 02:17:47 Re: [PATCH] Allow Postgres to pick an unused port to listen
Previous Message Kyotaro Horiguchi 2023-04-13 02:00:31 Re: Issue in postgres_fdw causing unnecessary wait for cancel request reply