Re: Inlining comparators as a performance optimisation - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Inlining comparators as a performance optimisation
Date
Msg-id CA+U5nMKm6a3SMZruAL3U+wGkTbX-2HEFLgMtSEqPVenHvoCmGA@mail.gmail.com
Whole thread Raw
In response to Re: Inlining comparators as a performance optimisation  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Sep 21, 2011 at 4:22 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Simon Riggs <simon@2ndQuadrant.com> writes:
>> This is a marvellous win, a huge gain from a small, isolated and
>> easily tested change. By far the smallest amount of additional code to
>> sorting we will have added and yet one of the best gains.
>
> I think you forgot your cheerleader uniform.

LOL. I'm happy whoever and whenever we get large wins like that.

Go Postgres!

> A patch along these lines
> is not going to be small, isolated, easily maintained, nor beneficial
> for any but a small number of predetermined datatypes.

That was the starting premise.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: HeapTupleSatisfiesToast not setting XMIN_COMMITTED?
Next
From: Merlin Moncure
Date:
Subject: Re: HeapTupleSatisfiesToast not setting XMIN_COMMITTED?