Re: Direct I/O - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: Direct I/O
Date
Msg-id CA+hUKGLUNv4vaBvMq3Kx6de32T9An2_KXC8Q0DqCY2jtHkfXvA@mail.gmail.com
Whole thread Raw
In response to Re: Direct I/O  (Noah Misch <noah@leadboat.com>)
Responses Re: Direct I/O  (Thomas Munro <thomas.munro@gmail.com>)
Re: Direct I/O  (Justin Pryzby <pryzby@telsasoft.com>)
List pgsql-hackers
On Sun, Apr 30, 2023 at 4:11 PM Noah Misch <noah@leadboat.com> wrote:
> Speaking of the developer-only status, I find the io_direct name more enticing
> than force_parallel_mode, which PostgreSQL renamed due to overuse from people
> expecting non-developer benefits.  Should this have a name starting with
> debug_?

Hmm, yeah I think people coming from other databases would be tempted
by it.  But, unlike the
please-jam-a-gather-node-on-top-of-the-plan-so-I-can-debug-the-parallel-executor
switch, I think of this thing more like an experimental feature that
is just waiting for more features to make it useful.  What about a
warning message about that at startup if it's on?



pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: replacing role-level NOINHERIT with a grant-level option
Next
From: Andrew Dunstan
Date:
Subject: Re: run pgindent on a regular basis / scripted manner