On 30/10/2018 15:03, p.piero...@mmbb.it wrote:
> I thought that the “BEGIN/END” block was used to create new transactions
> and that each of them could be managed individually.
In PL/pgSQL, BEGIN/END just create syntactic blocks, they don't manage
transactions.
COMMIT and ROLLBACK manage top-leve
Lombardia, 4 Lodi (LO)
M: +39 328 9035851
P: +39 075 8556435
W: www.mmbb.it
-Messaggio originale-
Da: Adrian Klaver
Inviato: martedì 30 ottobre 2018 15:06
A: p.piero...@mmbb.it; pgsql-gene...@postgresql.org
Oggetto: Re: Problem with stored procedure and nested transactions
On 10/30/18 7:03
15:06
A: p.piero...@mmbb.it; pgsql-gene...@postgresql.org
Oggetto: Re: Problem with stored procedure and nested transactions
On 10/30/18 7:03 AM, p.piero...@mmbb.it wrote:
> Hi everyone,
>
> I have problems with stored procedures introduced in version 11.
>
> I do not understand
On 10/30/18 7:03 AM, p.piero...@mmbb.it wrote:
Hi everyone,
I have problems with stored procedures introduced in version 11.
I do not understand how to create a nested transaction, in this
semplified example:
*create**or**replace**procedure*tst_prc(*inout*p_cod *text*)
*language*plpgsql *as
Hi everyone,
I have problems with stored procedures introduced in version 11.
I do not understand how to create a nested transaction, in this semplified
example:
create or replace procedure tst_prc(inout p_cod text) language plpgsql as
$procedure$
begin
p_cod := 'a';
begin
