Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id B01662E034D for ; Tue, 4 Dec 2007 14:08:03 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 17092-09 for ; Tue, 4 Dec 2007 14:07:58 -0400 (AST) Received: from lists.commandprompt.com (host-159.commandprompt.net [207.173.203.159]) by postgresql.org (Postfix) with ESMTP id 322452E0062 for ; Tue, 4 Dec 2007 14:07:58 -0400 (AST) Received: from perhan.alvh.no-ip.org (200-126-116-213.bk8-dsl.surnet.cl [200.126.116.213]) (authenticated bits=0) by lists.commandprompt.com (8.13.8/8.13.8) with ESMTP id lB4I5wTP012137 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 4 Dec 2007 10:06:01 -0800 Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 3EB9547C69; Tue, 4 Dec 2007 15:05:57 -0300 (CLST) Date: Tue, 4 Dec 2007 15:05:57 -0300 From: Alvaro Herrera To: Scott Whitney Cc: pgsql-admin@postgresql.org Subject: Re: PANIC: right sibling Message-ID: <20071204180557.GG4727@alvh.no-ip.org> References: <20071204170252.00BAA3F276D@mail.int.journyx.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071204170252.00BAA3F276D@mail.int.journyx.com> User-Agent: Mutt/1.5.16 (2007-06-11) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (lists.commandprompt.com [207.173.203.159]); Tue, 04 Dec 2007 10:06:01 -0800 (PST) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200712/11 X-Sequence-Number: 27528 Scott Whitney wrote: > I don't really understand the postings I've found on this issue. This has > been going on for quite some time, but now that I'm regularly vacuuming this > db, I was looking for any info on how to fix this problem...I don't even > know enough about it to know what to include in this message. Probably a REINDEX on the corrupted index would solve it. I'm not sure if there's a known bug in the version you're using. If there is, obviously you should upgrade to a fixed one. Otherwise you may be able to help us find it by saving the corrupted index before reindexing it, for examination. -- Alvaro Herrera Developer, http://www.PostgreSQL.org/ "The only difference is that Saddam would kill you on private, where the Americans will kill you in public" (Mohammad Saleh, 39, a building contractor)