pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedFrom: Laurenz Albe <laurenz.albe@cybertec.at>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Teja Jakkidi <teja.jakkidi05@gmail.com>
Cc: pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: Statement_timeout in procedure block
Date: Wed, 19 Jun 2024 17:06:41 +0200
Message-ID: <f53ee50dee32d8040be119234537dbb66562b981.camel@cybertec.at> (raw)
In-Reply-To: <114105.1718809113@sss.pgh.pa.us>
References: <E0175C30-9A8F-4648-A2D5-36908FF6F695@gmail.com>
<46a33904c2cd86718cb4d7a0291906a08b8e246a.camel@cybertec.at>
<114105.1718809113@sss.pgh.pa.us>
On Wed, 2024-06-19 at 10:58 -0400, Tom Lane wrote:
> Laurenz Albe <laurenz.albe@cybertec.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
view thread (6+ messages)
Message-ID: <f53ee50dee32d8040be119234537dbb66562b981.camel@cybertec.at>
Permalink: ../f53ee50dee32d8040be119234537dbb66562b981.camel@cybertec.at/
Also on: postgresql.org/message-id/f53ee50dee32d8040be119234537dbb66562b981.camel@cybertec.at
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: laurenz.albe@cybertec.at, tgl@sss.pgh.pa.us, teja.jakkidi05@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: Statement_timeout in procedure block
In-Reply-To: <f53ee50dee32d8040be119234537dbb66562b981.camel@cybertec.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox