From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | HeapTupleSatisfies micro tuning |
Date: | 2008-02-06 14:24:45 |
Message-ID: | 1202307885.29242.15.camel@ebony.site |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I note that in HeapTupleSatisfies... we call
TransactionIdIsCurrentTransactionId() explicitly and then call it again
in TransactionIdIsInProgress(). Which means we also end up checking
twice whether each xid is normal also.
It would seem easier to make a check TransactionIdIsRecent() early and
if true then check TransactionIdIsCurrentTransactionId() and then check
RecentTransactionIdIsInProgress(). That would avoid the multiple checks,
as well as save a few cycles since the IsCurrent check can be expensive
if we have many subtransactions.
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
From | Date | Subject | |
---|---|---|---|
Next Message | Staale Smedseng | 2008-02-06 14:30:56 | Re: Why are we waiting? |
PostgreSQL : 가능한 | Gevik Babakhani | 2008-02-06 13:59:31 | PostgreSQL : 가능한 범퍼카 토토 Windows |