Re: URGENT - HELP WITH 7.3.4 Strangeness - Mailing list pgsql-admin

From Chris Hoover
Subject Re: URGENT - HELP WITH 7.3.4 Strangeness
Date
Msg-id 41A2540F.2060402@sermonaudio.com
Whole thread Raw
In response to Re: URGENT - HELP WITH 7.3.4 Strangeness  ("Vishal Kashyap @ [SaiHertz]" <vishalonlist@gmail.com>)
List pgsql-admin
Actually,

We have 3 distinct db servers, each with separate db's on them.  There
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
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
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
down?  Of course, the db servers are all production, so we don't have
large windows to work with.

Thanks,

chris
Vishal Kashyap @ [SaiHertz] wrote:

>Chris ,
>
>
>
>
>>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.
>>
>>
>
>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
>
>
>
>
>
>



pgsql-admin by date:

Previous
From: "Vishal Kashyap @ [SaiHertz]"
Date:
Subject: Re: URGENT - HELP WITH 7.3.4 Strangeness
Next
From: "Greg Sabino Mullane"
Date:
Subject: Re: Stamping rows...