Re: BUG #14964: statement_timeout cann't set in plpgsql

On Mon, Dec 11, 2017 at 7:29 AM, <digoal(at)126(dot)com> wrote:

> The following bug has been logged on the website:
>
> Bug reference: 14964
> Logged by: Zhou Digoal
> Email address: digoal(at)126(dot)com
> PostgreSQL version: 10.1
> Operating system: centos 7.4 x64
> Description:
>
> ```
> create or replace function f1(int) returns setof record as $$
> declare
> begin
> set local statement_timeout='1ms';
> return query select count(*) as cnt, id from a where id<$1 group by id;
> end;
> $$ language plpgsql strict ;
> ```
>
> but it can execute every time, which when the query run more than 1ms.
>
>
​A quick Google search turns up the response that this is working as
designed. In short, the timeout applies to statements sent by the client.
Once changed the next statement the client sends to the server will use the
new setting. Since a server function invocation is a single statement as
far as the client-server relationship goes a timeout set within a function
will not apply until the statement the invoked the function ends and a new
statement is sent from the client to the server.

David J.