public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bruce Momjian <[email protected]>
To: Greg Smith <[email protected]>
Cc: PostgreSQL-documentation <[email protected]>
Subject: Re: [HACKERS] [PATCHES] [PERFORM] Direct I/O issues
Date: Wed, 7 Feb 2007 22:57:22 -0500 (EST)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
Greg Smith wrote:
> On Fri, 24 Nov 2006, Bruce Momjian wrote:
>
> > OK, I modified test_fsync.c by copying the defines from xlog.c, and
> > fixed the O_DIRECT alignment and check write()/fsync().
>
> I just tested your new test_fsync as included in the 8.2rc1, and it's
> working perfectly for me now on Linux. All the O_SYNC writes using
> O_DIRECT are reporting realistic timings. I'm happy that this code is
> working as it should and appreciate the quick response. I still think the
> wal_sync_method documentation deserves an update noting that O_DIRECT is
> used when available with the sync write methods.
O_DIRECT mention added, and backpatched to 8.2.X.
--
Bruce Momjian <[email protected]> http://momjian.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
Attachments:
[text/x-diff] /rtmp/diff (776B, 2-%2Frtmp%2Fdiff)
download | inline diff:
Index: doc/src/sgml/config.sgml
===================================================================
RCS file: /cvsroot/pgsql/doc/src/sgml/config.sgml,v
retrieving revision 1.108
diff -c -c -r1.108 config.sgml
*** doc/src/sgml/config.sgml 1 Feb 2007 00:28:16 -0000 1.108
--- doc/src/sgml/config.sgml 8 Feb 2007 03:52:01 -0000
***************
*** 1385,1390 ****
--- 1385,1391 ----
Not all of these choices are available on all platforms.
The default is the first method in the above list that is supported
by the platform.
+ The <literal>open_</>* options also use <literal>O_DIRECT</> if available.
This parameter can only be set in the <filename>postgresql.conf</>
file or on the server command line.
</para>
view thread (2+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: [HACKERS] [PATCHES] [PERFORM] Direct I/O issues
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox