Re: Abbreviated keys for text cost model fix - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Abbreviated keys for text cost model fix
Date
Msg-id CAM3SWZSnRAz0JqUMuhFE_uBgmiaQ_xd8FeLxPQvS30TpNVeCTw@mail.gmail.com
Whole thread Raw
In response to Re: Abbreviated keys for text cost model fix  (Jeremy Harris <jgh@wizmail.org>)
Responses Re: Abbreviated keys for text cost model fix  (Jeremy Harris <jgh@wizmail.org>)
List pgsql-hackers
On Tue, Feb 24, 2015 at 4:32 PM, Jeremy Harris <jgh@wizmail.org> wrote:
> On 23/02/15 16:40, Tomas Vondra wrote:
>> On 22.2.2015 22:30, Peter Geoghegan wrote:
>>> You should try it with the data fully sorted like this, but with one
>>> tiny difference: The very last tuple is out of order. How does that
>>> look?
>
> If this case is actually important, a merge-sort can take
> significant advantage of the partial order:

> test=# set enable_intmerge_sort to on;

What is this?

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Jeremy Harris
Date:
Subject: Re: Abbreviated keys for text cost model fix
Next
From: Kyotaro HORIGUCHI
Date:
Subject: Re: A typo in backend/replication/README