Alvaro Herrera <alvherre@xxxxxxxxxxxxxx> writes:
> Ok, so it seems the lockup occured only with the hash indexes? Then it
> means we still have bugs in the locking code for those.
"Still" meaning "in the version he's using", which he hasn't told us
anywhere that I saw. (Internal evidence suggests it's 7.3 something)
> It doesn't surprise me.
A deadlock in hash indexes wouldn't be surprising in pre-7.4 code,
since 7.4 was the first version that even pretended to be deadlock free
in hash indexes. But it does seem pretty surprising that the deadlock
checker didn't fire and boot somebody out of the deadlock. We haven't
had any bugs reported in deadlock detection in a very long time (since
7.1 I think). This could mean there's still something wrong in there.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
