> In the brave new world of WAL, Postgres does not flush dirty buffers
> disk at transaction commit, relying on WAL to clean up if a database
> system failure occurs. If we don't log page images to WAL then I
> there's a hole here wherein a Postgres crash can lose data even though
> no failure of the surrounding OS occurs. Maybe it's safe, but I'm not
It should be (imho *is*) safe for heap pages, but not for index pages.
The reasoning for heap pages is, that the WAL code (pre page image)
coped with future heap page versions.
I would not expect it to work for index pages, since one "feature" of
the page images was to "undo" future index operations.
pgsql-hackers by date
|Next:||From: John Gray||Date: 2001-11-27 11:25:55|
|Subject: Re: 7.2 stuff|
|Previous:||From: Zeugswetter Andreas SB SD||Date: 2001-11-27 09:14:46|
|Subject: Re: insert/update/delete statements returning a query response|