Re: SUBTRANS: Minimizing calls to SubTransSetParent() - Mailing list pgsql-hackers

From Tomas Vondra
Subject Re: SUBTRANS: Minimizing calls to SubTransSetParent()
Date
Msg-id 0476814e-e003-7609-0fc7-5eae36956fe3@enterprisedb.com
Whole thread Raw
In response to Re: SUBTRANS: Minimizing calls to SubTransSetParent()  (Simon Riggs <simon.riggs@enterprisedb.com>)
Responses Re: SUBTRANS: Minimizing calls to SubTransSetParent()
List pgsql-hackers

On 11/17/22 18:29, Simon Riggs wrote:
> On Thu, 17 Nov 2022 at 17:04, Simon Riggs <simon.riggs@enterprisedb.com> wrote:
>>
>> New version with greatly improved comments coming very soon.
> 
>>> Perhaps it would be a good idea to split up the patch.  The business
>>> about making pg_subtrans flat rather than a tree seems like a good
>>> idea in any event, although as I said it doesn't seem like we've got
>>> a fleshed-out version of that here.  We could push forward on getting
>>> that done and then separately consider the rest of it.
>>
>> Yes, I thought you might ask that so, after some thought, have found a
>> clean way to do that and have split this into two parts.
> 
> Attached.
> 
> 002 includes many comment revisions, as well as flattening the loops
> in SubTransGetTopmostTransaction and TransactionIdDidCommit/Abort
> 003 includes the idea to not-always do SubTransSetParent()
> 

I'm a bit confused by the TransactionIdsAreOnSameXactPage naming. Isn't
this really checking clog pages?


regards

-- 
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: ubsan fails on 32bit builds
Next
From: Robert Haas
Date:
Subject: Re: Reducing power consumption on idle servers