From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Vadim Mikheev <vmikheev(at)sectorbase(dot)com> |
Cc: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alfred Perlstein <bright(at)wintelcom(dot)net>, Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>, peter_e(at)gmx(dot)net, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: RE: [COMMITTERS] pgsql/src/backend/access/transam ( xact.c xlog.c) |
Date: | 2000-11-16 16:59:08 |
Message-ID: | 200011161659.LAA15203@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
[ Charset ISO-8859-1 unsupported, converting... ]
> > > > Earlier, Vadim was talking about arranging to share fsyncs of the WAL
> > > > log file across transactions (after writing your commit record to the
> > > > log, sleep a few milliseconds to see if anyone else fsyncs before you
> > > > do; if not, issue the fsync yourself). That would offer less-than-
> > > > one-fsync-per-transaction performance without giving up any
> > > > guarantees.
> > > > If people feel a compulsion to have a tunable parameter, let 'em tune
> > > > the length of the pre-fsync sleep ...
> > >
> > > Already implemented (without ability to tune this parameter -
> > > xact.c:CommitDelay, - yet). Currently CommitDelay is 5, so
> > > backend sleeps 1/200 sec before checking/forcing log fsync.
> >
> > But it returns _completed_ to the client before sleeping, right?
>
> No.
Ewe, so we have this 1/200 second delay for every transaction. Seems
bad to me.
--
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 | Bruce Momjian | 2000-11-16 17:03:39 | Re: AW: Coping with 'C' vs 'newC' function language namesh |
Previous Message | Tom Lane | 2000-11-16 16:20:58 | Re: [rfc] new CREATE FUNCTION (and more) |