| From: | Steve Atkins <steve(at)blighty(dot)com> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] fsync method checking |
| Date: | 2004-03-26 23:14:59 |
| Message-ID: | 20040326231459.GA23615@gp.word-to-the-wise.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
On Fri, Mar 26, 2004 at 07:25:53AM +0100, Manfred Spraul wrote:
> >Compare file sync methods with one 8k write:
> > (o_dsync unavailable)
> > open o_sync, write 6.270724
> > write, fdatasync 13.275225
> > write, fsync, 13.359847
> >
> >
> Odd. Which filesystem, which kernel? It seems fdatasync is broken and
> syncs the inode, too.
This may be relevant.
From the man page for fdatasync on a moderately recent RedHat installation:
BUGS
Currently (Linux 2.2) fdatasync is equivalent to fsync.
Cheers,
Steve
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-03-26 23:41:28 | Re: Per database users/admins, handy for database virtual hosting... |
| Previous Message | markw | 2004-03-26 22:00:01 | PostgreSQL block size vs. LVM2 stripe width |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-03-26 23:15:01 | Re: bigint index not used |
| Previous Message | Josh Berkus | 2004-03-26 23:11:22 | Re: postgres eating CPU on HP9000 |