| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, Marti Raudsepp <marti(at)juffo(dot)org>, Stephen Frost <sfrost(at)snowman(dot)net>, Greg Stark <stark(at)mit(dot)edu>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Thom Brown <thom(at)linux(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: B-Tree support function number 3 (strxfrm() optimization) |
| Date: | 2014-08-05 23:18:23 |
| Message-ID: | CAM3SWZS6fuCJ0QZeiNNiq5VeDpCzpnuuDie=2WpyyM54fjqchw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Aug 5, 2014 at 12:33 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> I'm also not sure it won't come up again. There are certainly other
> text-like datatypes out there that might want to optimize sorts; e.g.
> citext.
Fair enough. Actually, come to think of it I find BpChar/character(n)
a far more likely candidate. I've personally never used the SQL
standard character(n) type, which is why I didn't think of it until
now. TPC-H does make use of character(n) though, and that might be a
good reason in and of itself to care about its sorting performance.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2014-08-05 23:31:21 | Re: Pg_upgrade and toast tables bug discovered |
| Previous Message | Jeff Janes | 2014-08-05 22:05:54 | Re: Fixed redundant i18n strings in json |