RE: RE: [COMMITTERS] pgsql/src/backend/access/transam ( xact.c xlog.c)

From: "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>
To: "'Alfred Perlstein'" <bright(at)wintelcom(dot)net>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Don Baccus <dhogaza(at)pacifier(dot)com>, "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 21:26:15
Message-ID: 8F4C99C66D04D4118F580090272A7A234D3189@sectorbase1.sectorbase.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> > You are going to kernel call/yield anyway to fsync, so why
> > not try and if someone does the fsync, we don't need to do it.
> > I am suggesting re-checking the need for fsync after the return
> > from sleep(0).
>
> It might make more sense to keep a private copy of the last time
> the file was modified per-backend by that particular backend and
> a timestamp of the last fsync shared globally so one can forgo the
> fsync if "it hasn't been dirtied by me since the last fsync"
>
> This would provide a rendevous point for the fsync call although
> cost more as one would need to periodically call gettimeofday to
> set the modified by me timestamp as well as the post-fsync shared
> timestamp.

Already made, but without timestamps. WAL maintains last byte of log
written/fsynced in shmem, so XLogFlush(_last_byte_to_be_flushed_)
will do nothing if data are already on disk.

Vadim

Browse pgsql-hackers by date

  From Date Subject
Next Message Alfred Perlstein 2000-11-16 21:27:54 Re: RE: [COMMITTERS] pgsql/src/backend/access/transam ( xact.c xlog.c)
Previous Message Mikheev, Vadim 2000-11-16 21:11:54 RE: RE: [COMMITTERS] pgsql/src/backend/access/transam ( xact.c xlog.c)