From: Tom Lane <tgl@sss.pgh.pa.us>
To: MStringham@tomax.com
Cc: pgsql-admin@postgresql.org
Subject: Re: "PANIC: btree_split_redo: lost left sibling" problem
Date: Tue, 09 Dec 2008 17:01:10 -0500
Message-ID: <21696.1228860070@sss.pgh.pa.us> (raw)
In-Reply-To: <OFF3E761DE.99B8E506-ON87257515.00647BD8-87257515.00656A7C@tomax.com>
References: <OFF3E761DE.99B8E506-ON87257515.00647BD8-87257515.00656A7C@tomax.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, MStringham@tomax.com
Subject: Re: "PANIC: btree_split_redo: lost left sibling" problem
In-Reply-To: <21696.1228860070@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox