X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 2D64D52834 for ; Wed, 8 Jun 2005 16:26:30 -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 25452-05 for ; Wed, 8 Jun 2005 19:26:22 +0000 (GMT) Received: from koolancexeon.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by svr1.postgresql.org (Postfix) with ESMTP id DB36452851 for ; Wed, 8 Jun 2005 16:26:20 -0300 (ADT) Received: mail.g2switchworks.com 10.10.1.8 from 10.10.1.37 10.10.1.37 via HTTP with MS-WebStorage 6.5.6944 Received: from state.g2switchworks.com by mail.g2switchworks.com; 08 Jun 2005 14:26:21 -0500 Subject: Re: Indexes getting corrupted. From: Scott Marlowe To: "Bruno G. Albuquerque" Cc: pgsql-admin@postgresql.org In-Reply-To: <42A73B60.7010909@dba.com.br> References: <42A73B60.7010909@dba.com.br> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1118258780.5758.160.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Wed, 08 Jun 2005 14:26:21 -0500 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200506/53 X-Sequence-Number: 17808 On Wed, 2005-06-08 at 13:39, Bruno G. Albuquerque wrote: > I am having a weird problem here. I have the automated process to > install PostgreSQL (8.0.1) on Windows 2000 machines. Besides installing > the database server itself, my process does the following: > > 1 - Runs initdb to created the database I will be using. > 2 - Runs a SQL script that creates the entire database and populates > some of the tables. > 3 - Runs another script that populates other tables (using COPY). > > What happens is that, sometimes, after the entire process run, I end up > with a database with virtually all indexes corrupt! Try to use the > indexes for anything results in "index is not a btree" error. This > happens randomly and I can get it fixed sometimes by simply erasin > everything and starting over. Note that such behaviour is normally associated with bad hardware (RAM, hard drive, controller, CPU, you name it...) But since the windows port is pretty new, you may have found some corner case. Do you have a "pre-packaged" test case that induces failures most of the time or something like that? Are these machines all basically make/model/brand/chipset etc... of machines? Then it might be a buggy driver or something.