| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Teja Jakkidi <teja(dot)jakkidi05(at)gmail(dot)com>, pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Statement_timeout in procedure block |
| Date: | 2024-06-19 15:06:41 |
| Message-ID: | f53ee50dee32d8040be119234537dbb66562b981.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Wed, 2024-06-19 at 10:58 -0400, Tom Lane wrote:
> Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> writes:
> > What works is setting the parameter on the procedure:
>
> > test=> CREATE OR REPLACE PROCEDURE sit() LANGUAGE plpgsql SET statement_timeout = 2000 AS 'BEGIN PERFORM pg_sleep(5); END;';
> > CREATE PROCEDURE
>
> That doesn't work either, for me, and I would not expect any of these
> variants to do so.
Ah, you are right.
It was the SET statement in the previous incarnation of the procedure that
had changed the parameter for my database session.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kenneth Barber | 2024-06-19 15:18:57 | Excluding event triggers from a pg_dump |
| Previous Message | Tom Lane | 2024-06-19 14:58:33 | Re: Statement_timeout in procedure block |