From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
---|---|
To: | bright(at)wintelcom(dot)net |
Cc: | vmikheev(at)SECTORBASE(dot)COM, 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-11 09:02:37 |
Message-ID: | 20001111180237F.t-ishii@sra.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> * Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | J.J. Karels | 2000-11-11 09:36:35 | |
Previous Message | Bruce Momjian | 2000-11-11 08:07:12 | Re: RE: [COMMITTERS] pgsql/src/backend/access/transam ( xact.c xlog.c) |