| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Giles Lean <giles(at)nemeton(dot)com(dot)au> |
| Cc: | "Randall Parker" <randall(at)nls(dot)net>, "PostgreSQL-Dev" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: An idea on faster CHAR field indexing |
| Date: | 2000-06-22 03:18:19 |
| Message-ID: | 7122.961643899@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Giles Lean <giles(at)nemeton(dot)com(dot)au> writes:
> My only experience of this was tuning a sort utility, where the extra
> time to convert the strings with strxfrm() and the large additional
> memory requirement killed any advantage strcmp() had over strcoll().
> Whether this would be the case for database indexes in general or
> ideed ever I don't know.
Interesting. That certainly suggests strxfrm could be a loser for
a database index too, but I agree it'd be nice to see some actual
measurements rather than speculation.
What locale(s) were you using when testing your sort code? I suspect
the answers might depend on locale quite a bit...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-06-22 03:27:10 | Re: Big 7.1 open items |
| Previous Message | Tom Lane | 2000-06-22 03:14:50 | Re: Big 7.1 open items |