| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | Dave Cramer <pg(at)fastcrypt(dot)com>, Greg Nancarrow <gregn4422(at)gmail(dot)com>, David Rader <david(dot)rader(at)gmail(dot)com>, pgsql-jdbc(at)lists(dot)postgresql(dot)org, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Procedure support improvements |
| Date: | 2019-08-26 18:14:50 |
| Message-ID: | 9461.1566843290@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-jdbc |
Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> writes:
> Dave Cramer wrote:
> test=> BEGIN;
> BEGIN
> test=> CALL testproc();
> ERROR: invalid transaction termination
> CONTEXT: PL/pgSQL function testproc() line 1 at COMMIT
> What is the rationale for this?
A procedure shouldn't be able to force commit of the surrounding
transaction.
As Dave noted, what would be nicer is for procedures to be able
to start and commit autonomous transactions, without affecting
the state of the outer transaction. We haven't got that though,
and it looks like a lot of work to get there.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2019-08-26 18:31:44 | Re: Procedure support improvements |
| Previous Message | Tom Lane | 2019-08-26 18:11:09 | Re: mingw32 floating point diff |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2019-08-26 18:31:44 | Re: Procedure support improvements |
| Previous Message | Laurenz Albe | 2019-08-26 18:08:05 | Re: Procedure support improvements |