| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Geoghegan <peter(at)2ndquadrant(dot)com>, Jay Levitt <jay(dot)levitt(at)gmail(dot)com>, "Jim \"Decibel!\" Nasby" <decibel(at)decibel(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>, PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Progress on fast path sorting, btree index creation time |
| Date: | 2012-02-08 15:17:36 |
| Message-ID: | CA+TgmoYzA82HsT_+EYtPACx5vyLK+fB4fVaD3ykiE4TPoYTwiQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Feb 8, 2012 at 9:51 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> IMO this patch is already well past the point of diminishing returns in
> value-per-byte-added. I'd like to see it trimmed back to provide a fast
> path for just single-column int4/int8/float4/float8 sorts. The other
> cases aren't going to offer enough of a win to justify the code space.
I'm curious about how much we're gaining from the single-column
specializations vs. the type-specific specializations. I think I'm
going to go try to characterize that.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-02-08 15:19:40 | Re: ecpglib use PQconnectdbParams |
| Previous Message | Robert Haas | 2012-02-08 15:15:36 | Re: Progress on fast path sorting, btree index creation time |