| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Daniel Cristian Cruz" <cruz(at)senai-sc(dot)ind(dot)br> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #3731: ash table "PROCLOCK hash" corrupted |
| Date: | 2007-11-08 17:29:48 |
| Message-ID: | 27516.1194542988@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"Daniel Cristian Cruz" <cruz(at)senai-sc(dot)ind(dot)br> writes:
> A few moments ago I got the following message, but didn't found any
> reference on the internet (including lists).
> Nov 8 13:50:56 SERVER postgres[18874]: [5-1] user=XXX,db=XXXPANIC: hash
> table "PROCLOCK hash" corrupted
> The error showed after some query that where logged because were slow (more
> than 5 seconds), in which they had a very big list of values in a NOT IN
> clause (not sure if this caused the problem).
> I don't know if this is a bug or not.
Well, it shouldn't have happened, so either it's a bug or you had a
hardware glitch. But unless you can find a way to reproduce it I'm
not sure we can do much about it. I doubt your large NOT IN was
relevant --- more likely it'd be something associated with inter-process
interactions.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-11-08 17:50:55 | Re: Planner problems in 8.2.4 and 8.2.5 (was: Possible planner bug/regression introduced in 8.2.5) |
| Previous Message | Greg Sabino Mullane | 2007-11-08 16:44:11 | Re: Planner problems in 8.2.4 and 8.2.5 (was: Possible planner bug/regression introduced in 8.2.5) |