Re: [PATCHES] O_DIRECT for WAL writes - Mailing list pgsql-hackers

From Douglas McNaught
Subject Re: [PATCHES] O_DIRECT for WAL writes
Date
Msg-id m24qbpc4xd.fsf@Douglas-McNaughts-Powerbook.local
Whole thread Raw
In response to Re: [PATCHES] O_DIRECT for WAL writes  ("Jim C. Nasby" <decibel@decibel.org>)
List 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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: regression failure
Next
From: Josh Berkus
Date:
Subject: Re: PL/pgSQL Debugger Support