| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Rajan Bhide" <rbhide(at)nulinkinc(dot)com> |
| Cc: | pgsql-novice(at)postgresql(dot)org, " Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Bruno Wolff III" <bruno(at)wolff(dot)to>, "Oliver Fromme" <olli(at)lurza(dot)secnetix(dot)de> |
| Subject: | Re: !!URGENT!! Should I keep INDEX on the table? |
| Date: | 2004-05-24 06:14:54 |
| Message-ID: | 2717.1085379294@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
"Rajan Bhide" <rbhide(at)nulinkinc(dot)com> writes:
> 2)WARNING: specified item offset is too large
> PANIC: failed to add item to the page for "cdr_transid_key"
[blinks] Can you offer a reproducible test case for that one?
Your mail seems to mention a client bug (message ... while idle),
a server bug (the above), performance issues, and I'm not sure
what else. It would be well to try to subdivide your concerns.
I also wonder whether you might be suffering from flaky-hardware
problems, seeing that you are reporting at least two odd behaviors
that no one else has seen with PG 7.4.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rajan Bhide | 2004-05-24 07:11:13 | Re: !!URGENT!! Should I keep INDEX on the table? |
| Previous Message | Rajan Bhide | 2004-05-24 05:40:46 | Re: !!URGENT!! Should I keep INDEX on the table? |