From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> |
Cc: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>, "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Shouldn't flush dirty buffers at shutdown ? |
Date: | 2000-05-10 03:47:39 |
Message-ID: | 16509.957930459@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> writes:
> What I've never understood until recently is that even normal aborts(not
> in the middle of b-tree splitting) and normal shutdown could cause an
> inconsistency between heap and indices.
Yes. Since WAL will provide the real solution in 7.1, I think we need
only look for a simple stopgap answer for 7.0.x. Perhaps we could just
tweak bufmgr.c so that dirty buffers are flushed out on both transaction
commit and abort. That doesn't solve the consistency-after-crash issue,
but at least you can do an orderly shutdown of a postmaster without
fear. Is it worth trying to do more now, rather than working on WAL?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-05-10 04:31:03 | Re: 7.0 RPM? |
Previous Message | Tom Lane | 2000-05-10 03:43:55 | Re: Problems compiling version 7 |