Re: Why must AUTOCOMMIT be ON to do txn control in plpgsql procedure?

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Luca Ferrari <fluca1978(at)gmail(dot)com>, Bryn Llewellyn <bryn(at)yugabyte(dot)com>
Cc: pgsql-general list <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Why must AUTOCOMMIT be ON to do txn control in plpgsql procedure?
Date: 2019-08-07 14:19:49
Message-ID: a66efc71-6dca-0f46-d667-2fb29526c840@aklaver.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 8/7/19 12:15 AM, Luca Ferrari wrote:
> On Wed, Aug 7, 2019 at 12:19 AM Bryn Llewellyn <bryn(at)yugabyte(dot)com> wrote:
>> 1. my call p2() starts a txn.

> Luca
>
> P.S:
> I don't believe that asking on a public mailing list for a company to
> answer is the right thing to do, you can always ask themselves on your
> own.

Sort of moot as PROCEDURE is a Postgres feature not a company feature.

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Rob Sargent 2019-08-07 14:22:06 Re: pg_wal fills up on big update query
Previous Message Daniel Fink (PDF) 2019-08-07 13:34:39 pg_wal fills up on big update query