From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
---|---|
To: | David Rader <david(dot)rader(at)gmail(dot)com> |
Cc: | pgsql-jdbc(at)lists(dot)postgresql(dot)org |
Subject: | Re: Procedure support improvements |
Date: | 2019-07-24 11:09:02 |
Message-ID: | CADK3HH+P2tetetb4megAgF=XE+oRbMX0HKPodZQ2smtP_WspqA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-jdbc |
On Tue, 23 Jul 2019 at 22:00, David Rader <david(dot)rader(at)gmail(dot)com> wrote:
>
>
> On Tue, Jul 23, 2019 at 4:37 PM Dave Cramer <pg(at)fastcrypt(dot)com> wrote:
>
>> Hmmm who knew you couldn't call a procedure inside a transaction. That
>> just seems broken
>>
>>
> Yeah, the description in the docs is:
> "Transaction control is only possible in CALL or DO invocations from the
> top level or nested CALL or DO invocations without any other intervening
> command. "
> https://www.postgresql.org/docs/11/plpgsql-transactions.html
>
>
> Which means to be able to call procedures that use commit or rollback you
> have to be able to call them without a begin...
>
This makes calling procedures a mostly useless feature IMO. What's the
motivation to make this work?
Dave
From | Date | Subject | |
---|---|---|---|
Next Message | Suraj Kharage | 2019-07-24 11:38:15 | Issue in to_timestamp/to_date while handling the quoted literal string |
Previous Message | Imai, Yoshikazu | 2019-07-24 10:09:51 | RE: seems like a bug in pgbench -R |
From | Date | Subject | |
---|---|---|---|
Next Message | Matteo Melli | 2019-07-24 14:15:56 | [pgjdbc/pgjdbc] fcbbc3: Updated scram to version 2.0 (#1532) |
Previous Message | David Rader | 2019-07-24 01:59:52 | Re: Procedure support improvements |