"Steve McLellan" <smclellan@xxxxxxxxxx> writes: > lc_messages = 'en_US.UTF-8' > lc_monetary = 'en_US.UTF-8' > lc_numeric = 'en_US.UTF-8' > lc_time = 'en_US.UTF-8' BTW, aside from the points already made: the above indicates that you initialized your database in en_US.utf8 locale. This is not necessarily a good decision from a performance standpoint --- you might be much better off with C locale, and might even prefer it if you favor ASCII-order sorting over "dictionary" sorting. utf8 encoding might create some penalties you don't need too. This all depends on a lot of factors you didn't mention; maybe you actually need utf8 data, or maybe your application doesn't do many string comparisons and so isn't sensitive to the speed of strcoll() anyway. But I've seen it be a gotcha for people moving from MySQL, which AFAIK doesn't worry about honoring locale-specific sort order. regards, tom lane -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
