Tom Lane wrote:
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
I can unfortunatly conform that I'm also seeing this :-( I'm seeing it
in some kind of tight loop in the plpgsql regression test. Either that,
or it's just doing something *really* slowly. Doing some poking at it
with procexp I see it always being somewhere in a callstack that's
around:
Which test command is it executing exactly? I'm wondering about the
part of the test that exercises statement_timeout. Could we somehow
have broken the ability to detect timeout interrupts ... and if so, how?
It appears to hang in blockme() - so your guess seems correct.
Has anyone checked whether the backend still responds to SIGINT
with the patch in place?
After it hung, I issued pg_ctl -m fast -w stop and it stopped cleanly.
cheers
andrew
---------------------------(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
