Daniel Cristian Cruz wrote:
> 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).
Can you reproduce it? Have you seen it before?
> I don't know if this is a bug or not.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support