From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
---|---|
To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Direct I/O |
Date: | 2022-11-01 13:33:41 |
Message-ID: | 20221101133341.GX16921@telsasoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Nov 01, 2022 at 08:36:18PM +1300, Thomas Munro wrote:
> Hi,
>
> Here is a patch to allow PostgreSQL to use $SUBJECT. It is from the
> AIO patch-set[1]. It adds three new settings, defaulting to off:
>
> io_data_direct = whether to use O_DIRECT for main data files
> io_wal_direct = ... for WAL
> io_wal_init_direct = ... for WAL-file initialisation
You added 3 booleans, but I wonder if it's better to add a string GUC
which is parsed for comma separated strings. (By "better", I mean
reducing the number of new GUCs - which is less important for developer
GUCs anyway.)
DIO is slower, but not so much that it can't run under CI. I suggest to
add an 099 commit to enable the feature during development.
Note that this fails under linux with fsanitize=align:
../src/backend/storage/file/buffile.c:117:17: runtime error: member access within misaligned address 0x561a4a8e40f8 for type 'struct BufFile', which requires 4096 byte alignment
--
Justin
From | Date | Subject | |
---|---|---|---|
Next Message | Jonathan S. Katz | 2022-11-01 15:19:02 | Re: heavily contended lwlocks with long wait queues scale badly |
Previous Message | Peter Eisentraut | 2022-11-01 13:23:51 | Re: Privileges on PUBLICATION |