| From: | Peter Geoghegan <peter(at)2ndquadrant(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: To Do wiki |
| Date: | 2012-04-10 15:55:20 |
| Message-ID: | CAEYLb_UBE4kH33ZdOV58bWcDnurpP7z_eYQxvJOhEAnA=Oz60w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10 April 2012 16:40, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> On 10.04.2012 18:31, Jeff Janes wrote:
>> 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?
>
>
> Oh, sorry, you're right. I stand corrected.
There is an impedance mismatch between tuplesort_begin_heap and
tuplesort_begin_index_btree that prevented this from being done with
the initial commit. Strangely, the SortSupport commit message didn't
comment on this.
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2012-04-10 15:55:47 | Re: [JDBC] Regarding GSoc Application |
| Previous Message | Robert Haas | 2012-04-10 15:51:15 | Re: Last gasp |