Re: Disaster! - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: Disaster!
Date
Msg-id 20040126170300.K98100-100000@houston.familyhealth.com.au
Whole thread Raw
In response to Re: Disaster!  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Awesome Tom :)

I'm glad I happened to have all the data required on hand to fully analyze
the problem.   Let's hope this make this failure condition go away for all
future postgresql users :)

Chris

On Mon, 26 Jan 2004, Tom Lane wrote:

> Okay ... Chris was kind enough to let me examine the WAL logs and
> postmaster stderr log for his recent problem, and I believe that
> I have now achieved a full understanding of what happened.  The true
> bug is indeed somewhere else than slru.c, and we would not have found
> it if slru.c had had less-paranoid error checking.

<snip>



pgsql-hackers by date:

Previous
From: Michael Glaesemann
Date:
Subject: Re: Disaster!
Next
From: Michael Brusser
Date:
Subject: Corrupted db?