Re: pgsql-server: Add: > > * Allow buffered WAL writes

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: "Marc G(dot) Fournier" <scrappy(at)postgresql(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql-server: Add: > > * Allow buffered WAL writes
Date: 2004-08-14 04:10:36
Message-ID: 200408140410.i7E4AaK01582@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Marc G. Fournier wrote:
> > With Informix, the logic used by most customers I dealt with was that
> > unbuffered logging was too slow and they were willing to do a few rekeys
> > for the performance gain.
>
> I tend to agree with Tom that this is a bad idea, but ... if we do
> foolishly implement this, can it be a disfeature that is only available
> via a special configure flag on compile, that creates a special GUC
> variable that defaults to the standard behaviour?
>
> Basically, if you desire to risk cutting off your left hand for the sake
> of speed, put them through a couple of hoops to get there first ...

It isn't going to be any worse than fsync. At least the system is
consistent while fsync leaves it inconsistent. In cases where people
are using fsync, I bet some would prefer this middle ground.

Now if you want to make fsync have the same restriction, that would make
sense.

--
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-08-14 04:11:14 Re: pgsql-server: Add: > > * Allow buffered WAL writes
Previous Message Bruce Momjian 2004-08-14 04:09:02 Re: pgsql-server: Add: > > * Allow buffered WAL writes