From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: To Do wiki |
Date: | 2012-04-10 15:31:40 |
Message-ID: | CAMkU=1yFfWwiaN+fC+ZJHp-ewfGhaXy7oM56qKf1NH=-LDfZzQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Apr 9, 2012 at 11:27 PM, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> On 10.04.2012 03:32, Jeff Janes wrote:
>>
>> The To Do wiki says not to add things to the page with discussing here.
...
>
>> sort_support was implemented for plain tuple sorting only, To Do is
>> extend to index-creation sorts (item 2 from message
>> <1698(dot)1323222387(at)sss(dot)pgh(dot)pa(dot)us>)
>
>
> Index-creation sorts are already handled, Tom is referring to using the new
> comparator API for index searches in that email. The change would go to
> _bt_compare().
If I do "select count(distinct bid) from pgbench_accounts" I get many
calls to btint4fastcmp, but if I do "create index on pgbench_accounts
(bid)" I instead get many calls to btint4cmp. If the index build is
using SortSupport, shouldn't it also be calling btint4fastcmp like the
distinct does?
Cheers,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Meskes | 2012-04-10 15:34:27 | Re: ECPG FETCH readahead |
Previous Message | Atri Sharma | 2012-04-10 15:28:23 | Re: [JDBC] Regarding GSoc Application |