Re: [PATCH] Revert default wal_sync_method to fdatasync on Linux 2.6.33+
От | Tom Lane |
---|---|
Тема | Re: [PATCH] Revert default wal_sync_method to fdatasync on Linux 2.6.33+ |
Дата | |
Msg-id | 5948.1291685894@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: [PATCH] Revert default wal_sync_method to fdatasync on Linux 2.6.33+ (Josh Berkus <josh@agliodbs.com>) |
Ответы |
Re: [PATCH] Revert default wal_sync_method to fdatasync
on Linux 2.6.33+
Re: [PATCH] Revert default wal_sync_method to fdatasync on Linux 2.6.33+ Re: [PATCH] Revert default wal_sync_method to fdatasync on Linux 2.6.33+ |
Список | pgsql-hackers |
Josh Berkus <josh@agliodbs.com> writes: > Making it support O_DIRECT would be possible but more complex; I don't > see the point unless we think we're going to have open_sync_with_odirect > as a seperate option. 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. regards, tom lane
В списке pgsql-hackers по дате отправления: