"Daniel Cristian Cruz" <[EMAIL PROTECTED]> 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
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
