[HACKERS] TODO: Determine optimal fdatasync/fsync, O_SYNC/O_DSYNC options

Doesn't this exist in: src/tools/fsync? Do we just need to make it more user friendly? Joshua D. Drake -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 Providing the most comprehensive PostgreSQL solutions since

Re: [HACKERS] TODO: Determine optimal fdatasync/fsync, O_SYNC/O_DSYNC options

Joshua D. Drake [EMAIL PROTECTED] writes: Doesn't this exist in: src/tools/fsync? No, that only tells you if the various alternatives *work*. Not which one performs best. regards, tom lane ---(end of broadcast)--- TIP 1:

Re: [HACKERS] TODO: Determine optimal fdatasync/fsync, O_SYNC/O_DSYNC options

Tom, JD, No, that only tells you if the various alternatives *work*. Not which one performs best. Performs best is pretty elusive. On Solaris 10, for example, fdatasync does best on pgbench on x86, but opendatasync does best on DBT2 on Sparc. I'm not certain we can really determine this

Re: [HACKERS] TODO: Determine optimal fdatasync/fsync, O_SYNC/O_DSYNC options

Josh Berkus josh@agliodbs.com writes: Performs best is pretty elusive. On Solaris 10, for example, fdatasync does best on pgbench on x86, but opendatasync does best on DBT2 on Sparc. I'm not certain we can really determine this with any accuracy. Yeah, if it were easy we've have done it