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

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Subject: Re: TODO: Determine optimal fdatasync/fsync, O_SYNC/O_DSYNC options
Date: 2006-06-08 23:39:51
Message-ID: 200606081639.51579.josh@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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 with any accuracy.

--
--Josh

Josh Berkus
PostgreSQL @ Sun
San Francisco

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-06-08 23:56:47 Re: self-deadlock at FATAL exit of boostrap process on read error
Previous Message Tom Lane 2006-06-08 23:36:52 Re: TODO: Rename some /contrib modules from pg* to pg_*