Re: statement_timeout doesnt work within plpgsql by design? - Mailing list pgsql-hackers

From Robert Treat
Subject Re: statement_timeout doesnt work within plpgsql by design?
Date
Msg-id 200702201446.34139.xzilla@users.sourceforge.net
Whole thread Raw
In response to Re: statement_timeout doesnt work within plpgsql by design?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tuesday 20 February 2007 12:50, Tom Lane wrote:
> Robert Treat <xzilla@users.sourceforge.net> writes:
> > pagila=# create or replace function test() returns bool as $$ begin set
> > statement_timeout = 3000; perform pg_sleep(4) ; return true; end $$
> > language plpgsql;
> > CREATE FUNCTION
>
> statement_timeout is measured across an entire interactive command, not
> individual commands within a function; and the timeout that applies to
> an interactive command is determined at its beginning.  So the above
> doesn't do what you think.
>

Well, I'd be happy if it caused the entire function to bail out or if it 
caused individual statements within a function to bail out, but it does 
neither.  I can see how that would be a bit tricky to implement though. 

-- 
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL


pgsql-hackers by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: autovacuum next steps
Next
From: "Jonah H. Harris"
Date:
Subject: Re: New feature request: FlashBack Query