Received: from localhost (unknown [200.46.204.183])
	by mail.postgresql.org (Postfix) with ESMTP id 00138650508
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Tue,  9 Dec 2008 18:01:16 -0400 (AST)
Received: from mail.postgresql.org ([200.46.204.86])
	by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024)
	with ESMTP id 76923-01 for
	<pgsql-admin-postgresql.org@mail.postgresql.org>;
	Tue,  9 Dec 2008 18:01:12 -0400 (AST)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by mail.postgresql.org (Postfix) with ESMTP id 29EA7650510
	for <pgsql-admin@postgresql.org>; Tue,  9 Dec 2008 18:01:12 -0400 (AST)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id mB9M1Asj021697;
	Tue, 9 Dec 2008 17:01:10 -0500 (EST)
To: MStringham@tomax.com
cc: pgsql-admin@postgresql.org
Subject: Re: "PANIC: btree_split_redo: lost left sibling" problem 
In-reply-to: 
 <OFF3E761DE.99B8E506-ON87257515.00647BD8-87257515.00656A7C@tomax.com>
References: 
 <OFF3E761DE.99B8E506-ON87257515.00647BD8-87257515.00656A7C@tomax.com>
Comments: In-reply-to MStringham@tomax.com
	message dated "Thu, 04 Dec 2008 11:27:37 -0700"
Date: Tue, 09 Dec 2008 17:01:10 -0500
Message-ID: <21696.1228860070@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none
X-Spam-Level: 
X-Archive-Number: 200812/79
X-Sequence-Number: 30912

MStringham@tomax.com writes:
> Last night we ran out of disk space on our server and when I tried to 
> start  pg_ctl I got this error:
>  ** EnterpriseDB Dynamic Tuning Agent ************************
>         * System Utilization: 66 %                                  *
>         *   Database Version: 8.1.3.12                              *

Hmm, I would have thought that EDB were bright enough to not let their
customers still be running 8.1.3.

> 2008-12-04 10:20:47 MST PANIC:  btree_split_redo: lost left sibling

This looks a whole lot like a bug that was repaired in 8.1.4.  You're
missing nearly three years of other bug fixes, too.

I don't recall the details of this bug with full clarity, but I *think*
that you might be able to get out of this just by installing 8.1.latest
over your existing executables and then starting the DB.  The commit
log message makes it seem like that should work, anyway.  (Hmm ...
but it looks from the log like you already tried an archive recovery?
If so you'll probably have to start that over.)

			regards, tom lane