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 A028A3A534F for ; Mon, 22 Nov 2004 21:01:29 +0000 (GMT) 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 77837-01 for ; Mon, 22 Nov 2004 21:01:26 +0000 (GMT) Received: from mail.astudios.com (ns1.astudios.com [66.49.77.3]) by svr1.postgresql.org (Postfix) with ESMTP id D409A3A536F for ; Mon, 22 Nov 2004 21:01:22 +0000 (GMT) Thread-Index: AcTQ1mxoT4lZAhpMRaqRyOv09Pu9iA== Received: from [10.4.13.50] ([66.194.26.150]) by mail.astudios.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 22 Nov 2004 16:01:23 -0500 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.181 Content-class: urn:content-classes:message Message-ID: <41A2540F.2060402@sermonaudio.com> Importance: normal Date: Mon, 22 Nov 2004 16:03:11 -0500 From: "Chris Hoover" User-Agent: Mozilla Thunderbird 0.8 (X11/20040920) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Vishal Kashyap @ [SaiHertz]" Cc: Subject: Re: URGENT - HELP WITH 7.3.4 Strangeness References: <41A2347F.8030606@sermonaudio.com> <77b69d2104112212087dacd577@mail.gmail.com> In-Reply-To: <77b69d2104112212087dacd577@mail.gmail.com> X-Enigmail-Version: 0.86.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; format=flowed; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable X-OriginalArrivalTime: 22 Nov 2004 21:01:23.0328 (UTC) FILETIME=[6C63E000:01C4D0D6] X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200411/166 X-Sequence-Number: 15550 Actually, We have 3 distinct db servers, each with separate db's on them. There=20 are between 20 and 170 db's per server. I actually moved a db from db server 3 to the new db server and it=20 worked fine on the new db server. However, when we went to move it back = to either db server 2 or 3, the problem reappeared??? I think since it=20 worked fine on the move to the new db server, it eliminates corrupt = data. Is there a good way to test for a memory issue w/o bringing the servers=20 down? Of course, the db servers are all production, so we don't have=20 large windows to work with. Thanks, chris Vishal Kashyap @ [SaiHertz] wrote: >Chris , > > > =20 > >>Here is what is happening: >> >>1. Last Sunday, ran a reindex on all databases across our 3 = postgresql >>servers. This was done using the reindexdb script from the contrib >>directory. The reindex was prompted due to strangeness on db server = 1. >> =20 >> > >>From going through the full text I understand that db server 1 >database is on all the other server. >Now if this is true then db server 1 has some kinda Hardware issues. >Which leads to database corruption and same data was loaded on other >servers. >check end posts of this thread >http://archives.postgresql.org/pgsql-general/2003-11/msg01511.php > > > > > =20 >