Re: [PATCHES] Win32 CHECK_FOR_INTERRUPTS() performance - Mailing list pgsql-hackers

From Merlin Moncure
Subject Re: [PATCHES] Win32 CHECK_FOR_INTERRUPTS() performance
Date
Msg-id 6EE64EF3AB31D5448D0007DD34EEB3417DD685@Herge.rcsinc.local
Whole thread Raw
Responses Re: [PATCHES] Win32 CHECK_FOR_INTERRUPTS() performance
List pgsql-hackers
Tom wrote:
> "Merlin Moncure" <merlin.moncure@rcsonline.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(); // :-).




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCHES] Win32 CHECK_FOR_INTERRUPTS() performance
Next
From: Andrew Dunstan
Date:
Subject: Re: [PATCHES] Win32 CHECK_FOR_INTERRUPTS() performance