From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Shridhar Daithankar <shridhar_daithankar(at)myrealbox(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Background writer process |
Date: | 2003-11-14 18:52:32 |
Message-ID: | 200311141852.hAEIqWI27036@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Shridhar Daithankar wrote:
> >> Having fsync for regular data files and sync for WAL segment a comfortable
> >> compramise? Or this is going to use fsync for all of them.
>
> > I think we still need sync() for WAL because sometimes backends are
> > going to have to write their own buffers, and we don't want them using
> > fsync or it will be very slow.
>
> sync() for WAL is a complete nonstarter, because it gives you no
> guarantees at all about whether the write has occurred. I don't really
> care what you say about speed; this is a correctness point.
Sorry, I meant sync() is needed for recycling WAL (checkpoint), not for
WAL writes. I assume that's what Shridhar meant, but now I am not sure.
--
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
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2003-11-14 19:01:13 | Re: [PATCHES] ALTER TABLE modifications |
Previous Message | Tom Lane | 2003-11-14 18:49:59 | Re: Help with count(*) |