SEO

#1 (**permalink**) 04-11-2008, 06:23 AM

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(); // :-).

---------------------------(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

#2 (**permalink**) 04-11-2008, 06:23 AM

"Merlin Moncure" <merlin.moncure@rcsonline.com> writes:
> Tom wrote:
>> 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;

Thanks, fixed.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

Re: [PATCHES] Win32 CHECK_FOR_INTERRUPTS() performance