X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 1EF4BDA9EC for ; Wed, 26 Oct 2005 23:45:44 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 12947-02 for ; Thu, 27 Oct 2005 02:45:39 +0000 (GMT) Received: from wolff.to (wolff.to [66.93.197.194]) by svr1.postgresql.org (Postfix) with SMTP id 85079D84E9 for ; Wed, 26 Oct 2005 23:45:41 -0300 (ADT) Received: (qmail 5536 invoked by uid 500); 27 Oct 2005 02:47:28 -0000 Date: Wed, 26 Oct 2005 21:47:28 -0500 From: Bruno Wolff III To: Pieter-Jan Savat Cc: Tom Lane , pgsql-admin@postgresql.org Subject: Re: Memory/Performance issue: server closed the connection Message-ID: <20051027024728.GA32007@wolff.to> Mail-Followup-To: Bruno Wolff III , Pieter-Jan Savat , Tom Lane , pgsql-admin@postgresql.org References: <434B9169.6040404@barclab.com> <13658.1129038551@sss.pgh.pa.us> <434BDFE3.6040705@barclab.com> <14917.1129046286@sss.pgh.pa.us> <434CD4CA.60302@barclab.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <434CD4CA.60302@barclab.com> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 required=5 tests=[AWL=0.006] X-Spam-Level: X-Archive-Number: 200510/282 X-Sequence-Number: 19354 On Wed, Oct 12, 2005 at 11:18:02 +0200, Pieter-Jan Savat wrote: > > > Tom Lane wrote: > > >Pieter-Jan Savat writes: > > > > > >>2005-10-11 17:22:28 CEST (postgres@TheCore) [2005-10-11 17:08:49 CEST] > >>PANIC: right sibling's left-link doesn't match > >> > >> > > > >You've got a corrupt btree index. Try reindexing that table. > > > > regards, tom lane > > > > > You were right, thanks. > > But of course this is not something I would like to see in my production > database. Do you have > an idea what could be the cause of my corrupt index? This is probably hardware related. In particular using IDE drives with write caching turned on can cause problems if your server loses power. Not using ECC memory is another source of potential trouble.