From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | "Stephen C(dot) Tweedie" <sct(at)redhat(dot)com> |
Cc: | "Trond Eivind Glomsr?d" <teg(at)redhat(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: New Linux xfs/reiser file systems |
Date: | 2001-05-04 18:33:24 |
Message-ID: | 200105041833.f44IXOT02371@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Hi,
>
> On Fri, May 04, 2001 at 01:49:54PM -0400, Bruce Momjian wrote:
> > >
> > > Performance doing what? XFS has known performance problems doing
> > > unlinks and truncates, but not synchronous IO. The user should be
> > > using fdatasync() for databases, btw, not fsync().
> >
> > This is hugely helpful. In PostgreSQL 7.1, we do use fdatasync() by
> > default it is available on a platform.
>
> Good --- fdatasync is defined in SingleUnix, so it's probably safe to
> probe for it and use it by default if it is there.
>
> The 2.2 Linux kernel does not have fdatasync implemented, but glibc
> will fall back to fsync if that's all that the kernel supports. 2.4
> implements both with the required semantics.
OK, that is something we found too, that fdatasync() was there on some
platforms, but was really just an fsync(). I believe some HPUX
platforms had that.
OK, so they need a 2.4 kernel to properly test performance of Reiser/xfs
with fdatasync().
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Barry Lind | 2001-05-04 18:46:55 | Re: A bug with pgsql 7.1/jdbc and non-ascii (8-bit) chars? |
Previous Message | Bruno Wolff III | 2001-05-04 18:30:07 | Re: Case sensitive order by |