Re: Code checks for App Devs, using new options for transaction behavior - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Code checks for App Devs, using new options for transaction behavior
Date
Msg-id CANbhV-HprVyHjmCFDBHg0C3BTRW0YP8te7dZpT0z3B05vBzwHw@mail.gmail.com
Whole thread Raw
In response to Re: Code checks for App Devs, using new options for transaction behavior  (Simon Riggs <simon.riggs@enterprisedb.com>)
List pgsql-hackers
On Mon, 7 Nov 2022 at 14:25, Simon Riggs <simon.riggs@enterprisedb.com> wrote:
>
> On Wed, 2 Nov 2022 at 07:40, Simon Riggs <simon.riggs@enterprisedb.com> wrote:
>
> > > What will be the behavior if someone declares a savepoint with this
> > > name ("_internal_nested_xact").  Will this interfere with this new
> > > functionality?
> >
> > Clearly! I guess you are saying we should disallow them.
> >
> > > Have we tested scenarios like that?
> >
> > No, but that can be done.
>
> More tests as requested, plus minor code rework, plus comment updates.

New versions

-- 
Simon Riggs                http://www.EnterpriseDB.com/

Attachment

pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: ssl tests aren't concurrency safe due to get_free_port()
Next
From: walther@technowledgy.de
Date:
Subject: Re: fixing CREATEROLE