| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | "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 18:38:11 |
| Message-ID: | bdf3066b-8779-b76e-ea49-5866dbf6cbcb@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
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.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2020-08-25 18:59:50 | Re: ALTER SYSTEM between upgrades |
| Previous Message | Bruce Momjian | 2020-08-25 18:36:19 | Add comma after e.g. and i.e.? |