Re: [PATCHES] O_DIRECT for WAL writes

Douglas McNaught <doug@mcnaught.org>

From: Douglas McNaught <doug@mcnaught.org>
To: "Jim C. Nasby" <decibel@decibel.org>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Greg Stark <gsstark@mit.edu>, ITAGAKI Takahiro <itagaki.takahiro@lab.ntt.co.jp>, pgsql-hackers@postgresql.org
Date: 2005-06-23T18:18:54Z
Lists: pgsql-hackers
"Jim C. Nasby" <decibel@decibel.org> writes:

> Would testing in the WAL directory be sufficient? Or at least better
> than nothing? Of course we could test in the database directories as
> well, but you never know if stuff's been symlinked elsewhere... err, we
> can test for that, no?
>
> In any case, it seems like it'd be good to try to test and throw a
> warning if the drive appears to be caching or if we think the test might
> not cover everything (ie symlinks in the data directory).

I think it would make more sense to write the test as a separate
utility program--then the sysadmin can check the disks he cares
about.  I don't personally see the need to burden the backend with
this.

-Doug