From: | Jan Wieck <janwieck(at)Yahoo(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Adriaan Joubert <a(dot)joubert(at)albourne(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Re: WAL and commit_delay |
Date: | 2001-02-19 19:47:39 |
Message-ID: | 200102191947.OAA01924@jupiter.jw.home |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Adriaan Joubert <a(dot)joubert(at)albourne(dot)com> writes:
> > fdatasync() is available on Tru64 and according to the man-page behaves
> > as Tom expects. So it should be a win for us.
>
> Careful ... HPUX's man page also claims that fdatasync does something
> useful, but it doesn't. I'd recommend an experiment. Does today's
> snapshot run any faster for you (without -F) than before?
IIRC your HPUX manpage states that fdatasync() updates only
required information to find back the data. It sounded to me
that HPUX distinguishes between irrelevant inode info (like
modtime) and important things (like blocks).
But maybe I'm confused by HP and they can still tell me an X
for an U.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 2001-02-19 19:54:30 | Re: GET DIAGNOSTICS (was Re: Open 7.1 items) |
Previous Message | Tom Lane | 2001-02-19 17:36:19 | Re: GET DIAGNOSTICS (was Re: Open 7.1 items) |