| From: | "Vadim Mikheev" <vmikheev(at)sectorbase(dot)com> |
|---|---|
| To: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| 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 08:03:32 |
| Message-ID: | 007301c04fa3$b732d7c0$b67a30d0@sectorbase.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > > 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.
Vadim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zeugswetter Andreas SB | 2000-11-16 09:08:58 | AW: RE: [COMMITTERS] pgsql/src/backend/access/transam ( xact.c xlog.c) |
| Previous Message | Bruce Momjian | 2000-11-16 06:16:28 | Re: int4 or int32 |