| From: | AliE(at)atlas(dot)com |
|---|---|
| To: | hackers(at)postgreSQL(dot)org, scrappy(at)hub(dot)org |
| Cc: | 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: | Is there any way to check the status of the Index table. |
| Date: | 1998-05-11 15:39:44 |
| Message-ID: | E5B27B6CBA34D111B8FC0000C0105CF96ABCAB@ntserver3.atlas.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 1998-05-11 15:42:55 | Re: [HACKERS] Re: [QUESTIONS] money or dollar type |
| Previous Message | Brett McCormick | 1998-05-11 15:37:08 | Re: [HACKERS] Re: [PATCHES] Try again: S_LOCK reduced contentionh] |