Postgres Pro
Downloads
Home   >   mailing lists

Re: [PATCH] Revert default wal_sync_method to fdatasync on Linux 2.6.33+ - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: [PATCH] Revert default wal_sync_method to fdatasync on Linux 2.6.33+
Date
Msg-id 4CFD9658.6090304@agliodbs.com
Whole thread Raw
In response to Re: [PATCH] Revert default wal_sync_method to fdatasync on Linux 2.6.33+  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PATCH] Revert default wal_sync_method to fdatasync on Linux 2.6.33+  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view 
> Whether it's complex or not isn't really the issue.  The issue is that
> what test_fsync is testing had better match what the backend does, or
> people will be making choices based on not-comparable test results.
> I think we should have test_fsync just automatically fold in O_DIRECT
> the same way the backend does.

OK, patch coming then.  Right now test_fsync aborts when O_DIRECT fails.What should I have it do instead?

--                                  -- Josh Berkus                                    PostgreSQL Experts Inc.
                        http://www.pgexperts.com

pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: We really ought to do something about O_DIRECT and data=journalled on ext4
Next
From: Robert Haas
Date:
Subject: Re: We really ought to do something about O_DIRECT and data=journalled on ext4