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 149AE5284B for ; Wed, 8 Jun 2005 15:58:48 -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 19024-06 for ; Wed, 8 Jun 2005 18:58:39 +0000 (GMT) Received: from mail.jobflash.com (oncallweb2.jobflash.com [64.62.211.41]) by svr1.postgresql.org (Postfix) with ESMTP id 04E4C52849 for ; Wed, 8 Jun 2005 15:58:38 -0300 (ADT) Received: from [192.168.2.22] (user-2ivfinj.dialup.mindspring.com [165.247.202.243]) by mail.jobflash.com (Postfix) with ESMTP id 340ED42002; Wed, 8 Jun 2005 11:58:38 -0700 (PDT) Message-ID: <42A73FD7.40705@jobflash.com> Date: Wed, 08 Jun 2005 11:58:31 -0700 From: Tom Arthurs User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Bruno G. Albuquerque" Cc: pgsql-admin@postgresql.org Subject: Re: Indexes getting corrupted. References: <42A73B60.7010909@dba.com.br> In-Reply-To: <42A73B60.7010909@dba.com.br> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200506/52 X-Sequence-Number: 17807 Reindexdb in contrib should help with rebuilding indexes. 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. > > It happened in more thna one machine, if that matters. Also, changing > the database from one partition to another almost all the time solves it > (all machines have 2 partitions). > > Any ideas about what can be causing this? Manually doing "reindex index" > gets the indexes sorted. Is there a way to automatically reindex all > indexes in one go? that would at least help me a bit. > > Thanks in advance. > > -Bruno > > ********************************************************************** > Informação transmitida destina-se apenas à pessoa a quem foi endereçada > e pode conter informação confidencial, legalmente protegida e para > conhecimento exclusivo do destinatário. Se o leitor desta advertência > não for o seu destinatário, fica ciente de que sua leitura, divulgação > ou cópia é estritamente proibida. Caso a mensagem tenha sido recebida > por engano, favor comunicar ao remetente e apagar o texto de qualquer > computador. > > > The information transmitted is intended only for the person or entity to > which it is addressed and may contain confidential and/or privileged > material. Any review, retransmission, dissemination or other use of, or > taking of any action in reliance upon this information, by person or > entity other than the intended recipient is prohibited. If you received > this in error, please contact the sender and delete the material from > any computer. > ********************************************************************** > > ---------------------------(end of broadcast)--------------------------- > TIP 3: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly > > >