Re: RE: [COMMITTERS] pgsql/src/backend/access/transam ( xact.c xlog.c) - Mailing list pgsql-hackers

From Tatsuo Ishii
Subject Re: RE: [COMMITTERS] pgsql/src/backend/access/transam ( xact.c xlog.c)
Date
Msg-id 20001111180237F.t-ishii@sra.co.jp
Whole thread Raw
In response to Re: RE: [COMMITTERS] pgsql/src/backend/access/transam ( xact.c xlog.c)  (Alfred Perlstein <bright@wintelcom.net>)
List pgsql-hackers
> * Tatsuo Ishii <t-ishii@sra.co.jp> [001110 18:42] wrote:
> > > 
> > > Yes, though we can change this. We also can implement now
> > > feature that Bruce wanted so long and so much -:) -
> > > fsync log not on each commit but each ~ 5sec, if
> > > losing some recent commits is acceptable.
> > 
> > Sounds great.
> 
> Not really, I thought an ack on a commit would mean that the data
> is actually in stable storage, breaking that would be pretty bad
> no?  Or are you only talking about when someone is running with
> async Postgresql?
> 
> Although this doesn't have an effect on my current application,
> when running Postgresql with sync commits and WAL can one expect
> the old behavior, ie. success only after data and meta data (log)
> are written?

Probably you misunderstand what Bruce expected to have. He wished to
have not-everytime-fsync as an *option*. I believe we wil do strict
fsync in default.
--
Tatsuo Ishii


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: RE: [COMMITTERS] pgsql/src/backend/access/transam ( xact.c xlog.c)
Next
From: "J.J. Karels"
Date:
Subject: ...