Re: Optimizing TransactionIdIsCurrentTransactionId() - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Optimizing TransactionIdIsCurrentTransactionId()
Date
Msg-id CA+TgmoZhJ3w50Z+4f1kp7EZ0dOte9aEbM-j11xpfiFN3Dxb1XQ@mail.gmail.com
Whole thread Raw
In response to Re: Optimizing TransactionIdIsCurrentTransactionId()  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: Optimizing TransactionIdIsCurrentTransactionId()  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
On Fri, Dec 20, 2019 at 12:46 AM Simon Riggs <simon@2ndquadrant.com> wrote:
> If the TopTransactionId is not assigned, we can leave the whole function more quickly, not just avoid a test.

Those things are not really any different from each other. You leave
the function when you've done all the necessary tests....

> Read only transactions should have a fast path thru this function since they frequently read more data than write
transactions.

With regard to this point, I second Tomas's comments.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: ROS Didier
Date:
Subject: problem with read-only user
Next
From: Suraj Kharage
Date:
Subject: Re: backup manifests