Skip site navigation (1) Skip section navigation (2)

Re: URGENT - HELP WITH 7.3.4 Strangeness

From: "Chris Hoover" <revoohc(at)sermonaudio(dot)com>
To: "Vishal Kashyap (at) [SaiHertz]" <vishalonlist(at)gmail(dot)com>
Cc: <pgsql-admin(at)postgresql(dot)org>
Subject: Re: URGENT - HELP WITH 7.3.4 Strangeness
Date: 2004-11-22 21:03:11
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin

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.


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
>check end posts of this thread

In response to

pgsql-admin by date

Next:From: Greg Sabino MullaneDate: 2004-11-23 02:14:52
Subject: Re: Stamping rows...
Previous:From: Vishal Kashyap @ [SaiHertz]Date: 2004-11-22 20:08:07
Subject: Re: URGENT - HELP WITH 7.3.4 Strangeness

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group