Re: Shouldn't flush dirty buffers at shutdown ? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Shouldn't flush dirty buffers at shutdown ?
Date
Msg-id 16509.957930459@sss.pgh.pa.us
Whole thread Raw
In response to RE: Shouldn't flush dirty buffers at shutdown ?  ("Hiroshi Inoue" <Inoue@tpf.co.jp>)
Responses RE: Shouldn't flush dirty buffers at shutdown ?
smgrwrite() without LockBuffer(was RE: Shouldn't flush dirty buffers at shutdown ?)
List pgsql-hackers
"Hiroshi Inoue" <Inoue@tpf.co.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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [GENERAL] Problems compiling version 7
Next
From: "Hiroshi Inoue"
Date:
Subject: RE: Shouldn't flush dirty buffers at shutdown ?