From: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)edu>, <pgsql-hackers(at)postgresql(dot)org>, "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> |
Subject: | Re: [PATCHES] Win32 CHECK_FOR_INTERRUPTS() performance |
Date: | 2005-10-22 15:24:50 |
Message-ID: | 6BCB9D8A16AC4241919521715F4D8BCE92E77A@algol.sollentuna.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > 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
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2005-10-22 15:40:42 | Re: [PATCHES] Win32 CHECK_FOR_INTERRUPTS() performance |
Previous Message | Tom Lane | 2005-10-22 15:12:20 | Re: [PATCHES] Win32 CHECK_FOR_INTERRUPTS() performance |