Re: pgsql-server/src backend/storage/buffer/bufmgr ...

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Jan Wieck <JanWieck(at)Yahoo(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql-server/src backend/storage/buffer/bufmgr ...
Date: 2004-01-30 10:42:33
Message-ID: 200401301042.i0UAgX602991@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Jan Wieck wrote:
> Tom Lane wrote:
>
> > wieck(at)svr1(dot)postgresql(dot)org (Jan Wieck) writes:
> >> Added GUC variable bgwriter_flush_method controlling the action
> >> done by the background writer between writing dirty blocks and
> >> napping.
> >
> >> none (default) no action
> >> sync bgwriter calls smgrsync() causing a sync(2)
> >
> > Why would that be useful at all? I thought the purpose of the bgwriter
> > was to avoid I/O storms, not provoke them.
>
> Calling sync(2) every time the background writer naps means calling it
> every couple hundred milliseconds. That can hardly be called an IO
> storm, it's more like a constant breeze.

I talked to Jan about the idea of sync on every background writer sleep.
He is going to study the issue and report back.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2004-01-30 11:11:08 pgsql-server/doc TODO
Previous Message Bruce Momjian 2004-01-30 10:41:25 Re: pgsql-server/src backend/storage/buffer/bufmgr ...