Postgres Pro
Downloads
Home   >   mailing lists

Re: PL/pgSQL nested CALL with transactions - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: PL/pgSQL nested CALL with transactions
Date
Msg-id CAFj8pRBr7VY-TkV-xgCf7vRuEaO7mgSKhR7G31MQ0c+T-x1eVw@mail.gmail.com
Whole thread Raw
In response to Re: PL/pgSQL nested CALL with transactions  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: PL/pgSQL nested CALL with transactions  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view


2018-03-16 18:35 GMT+01:00 Peter Eisentraut <peter.eisentraut@2ndquadrant.com>:
On 3/16/18 00:24, Pavel Stehule wrote:
> What is benefit of DO command in PLpgSQL? Looks bizarre for me.

Not very typical, but we apply the same execution context handling to
CALL and DO at the top level, so it would be weird not to propagate that.

Although it is possible, I don't see any sense of introduction for DO into plpgsql. Looks like duplicate to EXECUTE.

 

--
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: PL/pgSQL nested CALL with transactions
Next
From: Tom Lane
Date:
Subject: Re: PL/pgSQL nested CALL with transactions