Re: Direct I/O

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Justin Pryzby <pryzby(at)telsasoft(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Direct I/O
Date: 2022-12-22 02:04:04
Message-ID: CA+hUKGLmeyrDcUYAty90V_YTcoo5kAFfQjRQ-_1joS_=X7HztA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Dec 14, 2022 at 5:48 PM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> 0001 -- David's palloc_aligned() patch https://commitfest.postgresql.org/41/3999/
> 0002 -- I/O-align almost all buffers used for I/O
> 0003 -- Add the GUCs
> 0004 -- Throwaway hack to make cfbot turn the GUCs on

David pushed the first as commit 439f6175, so here is a rebase of the
rest. I also fixed a couple of thinkos in the handling of systems
where we don't know how to do direct I/O. In one place I had #ifdef
PG_O_DIRECT, but that's always defined, it's just that it's 0 on
Solaris and OpenBSD, and the check to reject the GUC wasn't quite
right on such systems.

Attachment Content-Type Size
v3-0001-Introduce-PG_IO_ALIGN_SIZE-and-align-all-I-O-buff.patch text/x-patch 24.8 KB
v3-0002-Add-io_direct-setting-developer-only.patch text/x-patch 20.4 KB
v3-0003-XXX-turn-on-direct-I-O-by-default-just-for-CI.patch text/x-patch 749 bytes

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2022-12-22 02:25:03 Re: psql tab-complete
Previous Message Tom Lane 2022-12-22 01:50:39 Re: Optimization issue of branching UNION ALL