| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Per-column collation |
| Date: | 2010-11-22 20:06:43 |
| Message-ID: | 1290456403.471.3.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On tor, 2010-11-18 at 21:37 +0200, Heikki Linnakangas wrote:
> Have you done any performance testing? Functions like text_cmp can be
> a hotspot in sorting, so any extra overhead there might be show up in
> tests.
Without having optimized it very much yet, the performance for a 1GB
ORDER BY is
* without COLLATE clause: about the same as without the patch
* with COLLATE clause: about 30%-50% slower
I can imagine that there is some optimization potential in the latter
case. But in any case, it's not awfully slow.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2010-11-22 20:12:45 | Re: Per-column collation |
| Previous Message | Robert Haas | 2010-11-22 19:27:43 | Re: Re: Proposed Windows-specific change: Enable crash dumps (like core files) |