From: | ocie(at)paracel(dot)com |
---|---|
To: | AliE(at)atlas(dot)com |
Cc: | hackers(at)postgreSQL(dot)org, scrappy(at)hub(dot)org, DeeL(at)atlas(dot)com, BobbS(at)atlas(dot)com, Hari_Harikumar(at)prepaid(dot)atlas(dot)com, Thoi_Sieu-hoa(at)atlas(dot)com, JephK(at)atlas(dot)com, David_Schanen(at)atlas(dot)com |
Subject: | Re: [HACKERS] Is there any way to check the status of the Index table. |
Date: | 1998-05-11 20:54:26 |
Message-ID: | 9805112054.AA04583@dolomite.paracel.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
AliE(at)atlas(dot)com wrote:
>
> We installed the 6.3.2 on our system and now the nature of our data
> corruption has changed. It used to give us "BTP_CHAIN errors " message
> but now it is doing a core dump. I have two questions.
>
> 1. Is there a way to check the status of the Index files to see if they
> are OK and not corrupted? Since I did not know of anyway to test the
> index files, We tried to start the system without reindexing and it
> failed, yet after rendering, it works fine for almost a day. The
> corruption happens almost after the pick hour everyday.
> 2. Do you know of a good way to read the Core Dump file? We have FreeBsd
> Unix and I have tried to read the file with "gdb -c coredumpfile.core"
> command, but it complains about the format of the file. Any clue?
It also needs to know which executable produced the core file. I
usually omit the -c, simply "gcc <executable> <core file>".
Hope this helps,
Ocie
From | Date | Subject | |
---|---|---|---|
Next Message | ocie | 1998-05-11 20:56:25 | Re: [HACKERS] mmap and MAP_ANON |
Previous Message | Roelof Osinga | 1998-05-11 20:06:49 | Re: [QUESTIONS] locks |