Re: What happened to open_sync_without_odirect? - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: What happened to open_sync_without_odirect?
Date
Msg-id 201101160030.p0G0UKc15365@momjian.us
Whole thread Raw
In response to What happened to open_sync_without_odirect?  (Josh Berkus <josh@agliodbs.com>)
Responses Re: What happened to open_sync_without_odirect?  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
Josh Berkus wrote:
> Last I remember, we were going to add this as an option.  But I don't
> see a patch in the queue.  Am I missing it?  Was I supposed to write it?

I don't know, but let me add that I am confused how this would look to
users.  In many cases, kernels don't even support O_DIRECT, so what
would we do to specify this?  What about just auto-disabling O_DIRECT if
the filesystem does not support it; maybe issue a log message about it.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: New test_fsync messages for direct I/O
Next
From: Andrew Dunstan
Date:
Subject: Re: textarray option for file FDW