Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

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: Mon, 24 Oct 2005 10:55:37 -0400
  • Message-id: <6EE64EF3AB31D5448D0007DD34EEB3417DD685(at)Herge(dot)rcsinc(dot)local>

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





Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group