Re: Code checks for App Devs, using new options for transaction behavior

On Mon, Oct 31, 2022 at 4:23 PM Dilip Kumar <dilipbalaut(at)gmail(dot)com> wrote:
>
> On Sun, Oct 30, 2022 at 11:32 PM Simon Riggs
> <simon(dot)riggs(at)enterprisedb(dot)com> wrote:
> >
> > On Fri, 28 Oct 2022 at 10:33, Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com> wrote:
> >
> > > Thanks for the feedback, I will make all of those corrections in the
> > > next version.
> >
> > New version attached. I've rolled 002-004 into one patch, but can
> > split again as needed.
>
> I like the idea of "parse only" and "nested xact", thanks for working
> on this. I will look into patches in more detail, especially nested
> xact. IMHO there is no point in merging "nested xact" and "rollback on
> commit". They might be changing the same code location but these two
> are completely different ideas, in fact all these three should be
> reviewed as three separate threads as you mentioned in the first email
> in the thread.

What is the behavior if "nested_transactions" value is changed within
a transaction execution, suppose the value was on and we have created
a few levels of nested subtransactions and within the same transaction
I switched it to off or to outer?

--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com