Re: What happened to open_sync_without_odirect?

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: What happened to open_sync_without_odirect?
Date: 2011-01-16 00:30:20
Message-ID: 201101160030.p0G0UKc15365@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2011-01-16 00:41:13 Re: textarray option for file FDW
Previous Message Bruce Momjian 2011-01-16 00:15:04 New test_fsync messages for direct I/O