[HACKERS] fsync, fdatasync, open_sync, and open_datasync, -- Linux insanity

2004-08-11 Thread pgsql
Maybe I'm losing it, but I forced to apologize for trying to push for open_sync as the default. I have spent the last few days trying to come to some solid, documented and verifyable, conclusions about which is the best fsync method. At a minimum, what is the best fsync method for Linux. I can't

Re: [HACKERS] fsync, fdatasync, open_sync, and open_datasync, -- Linux insanity

2004-08-11 Thread Tom Lane
[EMAIL PROTECTED] writes: What would be a good strategy for addressing this issue? Is it an issue at all? Is it simply a documentation issue? Do we craft some sort of test that can characterize the behavior? What would that test need to do? It seems to me that it's a documentation issue.

Re: [HACKERS] fsync, fdatasync, open_sync, and open_datasync, --

2004-08-11 Thread Andreas Pflug
Tom Lane wrote: Andreas Pflug [EMAIL PROTECTED] writes: Tom Lane wrote: I don't think any test that we could build would be as useful as simply trying the different settings with an installation's real workload. Benchmarking the real workload isn't always so easy, and might be quite time

Re: [HACKERS] fsync, fdatasync, open_sync, and open_datasync, -- Linux insanity

2004-08-11 Thread Tom Lane
Andreas Pflug [EMAIL PROTECTED] writes: Tom Lane wrote: I don't think any test that we could build would be as useful as simply trying the different settings with an installation's real workload. Benchmarking the real workload isn't always so easy, and might be quite time consuming to

Re: [HACKERS] fsync, fdatasync, open_sync, and open_datasync, --

2004-08-11 Thread Andreas Pflug
Tom Lane wrote: I don't think any test that we could build would be as useful as simply trying the different settings with an installation's real workload. Benchmarking the real workload isn't always so easy, and might be quite time consuming to obtain meaningful values. Don't you think that some