Re: [PATCHES] Win32 CHECK_FOR_INTERRUPTS() performance

From: "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCHES] Win32 CHECK_FOR_INTERRUPTS() performance
Date: 2005-10-24 14:55:37
Message-ID: 6EE64EF3AB31D5448D0007DD34EEB3417DD685@Herge.rcsinc.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom wrote:
> "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> writes:
> > 3. A pl/pgsql function stuck in a empty loop is unkillable except
by
> > killing the process on the server, which cycles the entire server.
This
> > was the behavior before the patch, btw.
>
> Hmm, that suggests we need another CHECK_FOR_INTERRUPTS somewhere in
> plpgsql. Please show the exact test case you were using.

create function test_func() returns int4 as $$ BEGIN LOOP END LOOP;
select 0; END; $$ language plpgsql;

select test_func(); // :-).

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2005-10-24 15:04:13 Re: [PATCHES] Win32 CHECK_FOR_INTERRUPTS() performance
Previous Message Marc G. Fournier 2005-10-24 14:51:26 PostgreSQL 8.1 Beta 4