Re: Optimizing TransactionIdIsCurrentTransactionId()

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Optimizing TransactionIdIsCurrentTransactionId()
Date: 2019-12-20 13:07:00
Message-ID: CA+TgmoZhJ3w50Z+4f1kp7EZ0dOte9aEbM-j11xpfiFN3Dxb1XQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Dec 20, 2019 at 12:46 AM Simon Riggs <simon(at)2ndquadrant(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Suraj Kharage 2019-12-20 13:24:20 Re: backup manifests
Previous Message ROS Didier 2019-12-20 13:01:50 problem with read-only user