Re: Abbreviated keys for text cost model fix

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Jeremy Harris <jgh(at)wizmail(dot)org>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Abbreviated keys for text cost model fix
Date: 2015-02-25 00:42:19
Message-ID: CAM3SWZSnRAz0JqUMuhFE_uBgmiaQ_xd8FeLxPQvS30TpNVeCTw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Feb 24, 2015 at 4:32 PM, Jeremy Harris <jgh(at)wizmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro HORIGUCHI 2015-02-25 01:20:15 Re: A typo in backend/replication/README
Previous Message Jeremy Harris 2015-02-25 00:32:12 Re: Abbreviated keys for text cost model fix