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

From: Luca Ferrari <fluca1978(at)gmail(dot)com>
To: Benedict Holland <benedict(dot)m(dot)holland(at)gmail(dot)com>
Cc: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Bryn Llewellyn <bryn(at)yugabyte(dot)com>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, 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-08 08:19:59
Message-ID: CAKoxK+6BvHHKaS1GVE6Meyf-U7CYNkGYWHknaKs=6-+YN5krXQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Aug 7, 2019 at 11:36 PM Benedict Holland
<benedict(dot)m(dot)holland(at)gmail(dot)com> wrote:
>
> Also, I have never seen a rollback at the start of a proc. A pure hypothetical is that it is doing nothing or definitely not what you think it is.

That's my point, thanks.

Luca

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Thomas Kellerer 2019-08-08 09:06:11 lead() with arrays - strange behaviour
Previous Message Rob Sargent 2019-08-08 00:36:35 Re: Guidance needed on an alternative take on common prefix SQL