Re: Abbreviated keys for Datum tuplesort (was: Re: B-Tree support function number 3 (strxfrm() optimization)) - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Abbreviated keys for Datum tuplesort (was: Re: B-Tree support function number 3 (strxfrm() optimization))
Date
Msg-id CA+TgmoY=bWL5rs=0xhLUod-3cLxBKr1Ap45T=a_mSKsTrXkoRg@mail.gmail.com
Whole thread Raw
In response to Abbreviated keys for Datum tuplesort (was: Re: B-Tree support function number 3 (strxfrm() optimization))  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
Responses Re: Abbreviated keys for Datum tuplesort (was: Re: B-Tree support function number 3 (strxfrm() optimization))
Re: Re: Abbreviated keys for Datum tuplesort
List pgsql-hackers
On Fri, Jan 23, 2015 at 4:13 PM, Andrew Gierth
<andrew@tao11.riddles.org.uk> wrote:
> [pruning the Cc: list and starting a new thread]
>
> Here's the cleaned-up version of the patch to allow abbreviated keys
> when sorting a single Datum. This also removes comments that suggest
> that the caller of tuplesort_begin_datum should ever have to care
> about the abbreviated key optimization.
>
> I'll add this to the CF.

I think this is a good idea.  Do you have a test case that shows the benefit?

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



pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: New CF app deployment
Next
From: Peter Geoghegan
Date:
Subject: Re: Abbreviated keys for Datum tuplesort (was: Re: B-Tree support function number 3 (strxfrm() optimization))