> > 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?
Does that test run in the pl/pgsql test, using pl/pgsql code? If so it's quite likely - it doesn't crash, and it does *something*. And it's signal related... Could be if we waited long enough (>8 hours!) it goes on with an error. > Has anyone checked whether the backend still responds to > SIGINT with the patch in place? Nope, sorry. If nobody else beats me, I can hopefully take alook at it tomorrow. Just heading out now, so I can't check now. //Magnus ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org