| From: | Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com> |
|---|---|
| To: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
| Cc: | Erik Rijkers <er(at)xs4all(dot)nl>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Code checks for App Devs, using new options for transaction behavior |
| Date: | 2022-10-31 12:43:13 |
| Message-ID: | CANbhV-EssvggcHcS4+Z4Na0AYFMkT4c7LvUzd=pjT_jM8ugXZw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 31 Oct 2022 at 11:33, Dilip Kumar <dilipbalaut(at)gmail(dot)com> wrote:
> 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?
Patch does the same dance as with other xact variables.
XactNesting is the value within the transaction and in the patch this
is not exported, so cannot be set externally.
XactNesting is set at transaction start to the variable
DefaultXactNesting, which is set by the GUC.
So its not a problem, but thanks for checking.
--
Simon Riggs http://www.EnterpriseDB.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Korotkov | 2022-10-31 12:45:55 | Re: Proposal to use JSON for Postgres Parser format |
| Previous Message | Alexander Korotkov | 2022-10-31 12:38:46 | Re: heavily contended lwlocks with long wait queues scale badly |