Re: Optimizing TransactionIdIsCurrentTransactionId()

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Optimizing TransactionIdIsCurrentTransactionId()
Date: 2019-12-20 17:46:34
Message-ID: 7796.1576863994@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> On Fri, 20 Dec 2019 at 13:07, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> With regard to this point, I second Tomas's comments.

> I also agree with Tomas' comments. I am explaining *why* it will be an
> improvement, expanding on my earlier notes.
> This function is called extremely frequently in query processing and is
> fairly efficient. I'm pointing out cases where making it even quicker makes
> sense.

I think the point is that you haven't demonstrated that this particular
patch makes it quicker.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2019-12-20 17:57:55 Re: Optimizing TransactionIdIsCurrentTransactionId()
Previous Message Alvaro Herrera 2019-12-20 17:43:21 Re: range_agg