Re: wal_synch_method = open_sync safe on RHEL 5.5? - Mailing list pgsql-performance

From Greg Smith
Subject Re: wal_synch_method = open_sync safe on RHEL 5.5?
Date
Msg-id 4C1AE820.6020506@2ndquadrant.com
Whole thread Raw
In response to wal_synch_method = open_sync safe on RHEL 5.5?  (Mark Kirkwood <mark.kirkwood@catalyst.net.nz>)
Responses Re: wal_synch_method = open_sync safe on RHEL 5.5?
Re: wal_synch_method = open_sync safe on RHEL 5.5?
List pgsql-performance
Mark Kirkwood wrote:
Now I recall some discussion about this enabling direct io and the general flakiness of this on Linux, so is the option regarded as safe?

No one has ever refuted the claims in http://archives.postgresql.org/pgsql-hackers/2007-10/msg01310.php that it can be unsafe under a heavy enough level of mixed load on RHEL5.  Given the performance benefits are marginal on ext3, I haven't ever considered it worth the risk.  (I've seen much larger gains on Linux+Veritas VxFS).  From what I've seen, recent Linux kernel work has reinforced that the old O_SYNC implementation was full of bugs now that more work is being done to improve that area.  My suspicion (based on no particular data, just what I've seen it tested with) is that it only really worked before in the very specific way that Oracle does O_SYNC writes, which is different from what PostgreSQL does.

P.S. Be wary of expecting pgbench to give you useful numbers on a single run.  For the default write-heavy test, I recommend three runs of 10 minutes each (-T 600 on recent PostgreSQL versions) before I trust any results it gives.  You can get useful data from the select-only test in only a few seconds, but not the one that writes a bunch.

-- 
Greg Smith  2ndQuadrant US  Baltimore, MD
PostgreSQL Training, Services and Support
greg@2ndQuadrant.com   www.2ndQuadrant.us

pgsql-performance by date:

Previous
From: Mark Kirkwood
Date:
Subject: wal_synch_method = open_sync safe on RHEL 5.5?
Next
From: Mark Mielke
Date:
Subject: Re: wal_synch_method = open_sync safe on RHEL 5.5?