On Fri, Nov 12, 2010 at 12:45 AM, Gabriele Bartolini
gabriele.bartol...@2ndquadrant.it wrote:
Hi Mark,
Il 12/11/10 03:31, mark ha scritto:
I have listed what I think I will be doing with regards to initdb. if
anyone
sees problems with the following mixture during my dump - init-
restore
mark wrote:
A fix being so that col LIKE 'foo%' could use btree indexes in
locales like en_US.UTF8 (and probably some others).
How about specifying an opclass?:
http://www.postgresql.org/docs/current/interactive/indexes-opclass.html
-Kevin
--
Sent via pgsql-hackers mailing list
With how similar straight C and en_US.UTF8 are it was suggested to me,
by persons who are far more C knowledgeable then I in my office, that
this is something the PG community could fix . A fix being so that
col LIKE 'foo%' could use btree indexes in locales like en_US.UTF8
(and probably
Robert Haas robertmh...@gmail.com writes:
With how similar straight C and en_US.UTF8 are it was suggested to me,
by persons who are far more C knowledgeable then I in my office, that
this is something the PG community could fix . A fix being so that
col LIKE 'foo%' could use btree indexes in
On Fri, Nov 12, 2010 at 12:03 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
With how similar straight C and en_US.UTF8 are it was suggested to me,
by persons who are far more C knowledgeable then I in my office, that
this is something the PG community could
