| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Robin Abbi <robin(dot)abbi(at)downley(dot)net>, Dave Cramer <davecramer(at)postgres(dot)rocks>, Pg Docs <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Procedures |
| Date: | 2020-08-25 19:03:13 |
| Message-ID: | 20200825190313.GE26852@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Tue, Aug 25, 2020 at 08:38:11PM +0200, Peter Eisentraut wrote:
> On 2020-08-24 18:00, Bruce Momjian wrote:
> > - command, a procedure is called explicitly using
> > - the <xref linkend="sql-call"/> statement.
> > + command, a procedure is called in isolation using
> > + the <xref linkend="sql-call"/> command. If the CALL command is not
> > + part of an explicit transaction, a procedure can commit, rollback,
> > + and begin new transactions during its execution, which is not possible
> > + in functions.
>
> There are additional conditions for when a procedure can do transaction
> control, and it also depends on the language. It's not clear how much
> detail we should give in a general section like this. Often people read
> this and then wonder why it doesn't work.
I have updated the patch to mention it is dependend on the server-side
language.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
| Attachment | Content-Type | Size |
|---|---|---|
| proc.diff | text/x-diff | 854 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Erik Rijkers | 2020-08-25 19:03:34 | Re: Add comma after e.g. and i.e.? |
| Previous Message | Bruce Momjian | 2020-08-25 18:59:50 | Re: ALTER SYSTEM between upgrades |