Re: O_DIRECT on macOS - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: O_DIRECT on macOS
Date
Msg-id CA+hUKG+u12tTA3+6R4i-F1A0we3A=LEEwvb_pzM14gpLa5CXOQ@mail.gmail.com
Whole thread Raw
In response to Re: O_DIRECT on macOS  (Justin Pryzby <pryzby@telsasoft.com>)
List pgsql-hackers
On Mon, May 31, 2021 at 4:19 AM Justin Pryzby <pryzby@telsasoft.com> wrote:
> Should there be an "else" to warn/error in the case that "direct" is requested
> but not supported?

The way we use O_DIRECT currently is extremely minimal, it's just "if
you've got it, we'll use it, but otherwise not complain", and I wasn't
trying to change that yet, but you're right that if we add explicit
GUCs to turn on direct I/O for WAL and data files we should definitely
not let you turn them on if we can't do it.



pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: O_DIRECT on macOS
Next
From: Tom Lane
Date:
Subject: Re: postgres_fdw batching vs. (re)creating the tuple slots