Hello, I want to have pg use fast indexing for ~ operator. Is setting
C locale for this is still necessary? If yes, is it enough to
initdb/createdb with C locale? If it is not enough, why setting locale
to C and starting postmaster still gives other locale, for example,
pl_PL, in
postmaster log "i
On Thu, Jul 05, 2007 at 02:11:24PM +0200, Artur Rataj wrote:
> But I want the server to use the C locale. I set the locale to C and
> run postmaster. I supposed it uses C locale, but -d 5 shows in log:
The locale is decided when you run initdb. Once the cluster has been
created you can't change it
On 7/5/07, Artur Rataj <[EMAIL PROTECTED]> wrote:
But I want the server to use the C locale. I set the locale to C and
run postmaster. I supposed it uses C locale, but -d 5 shows in log:
The locale for indexing is set during initdb:
initdb --no-locale
The ~ operator does consider using btree r
But I want the server to use the C locale. I set the locale to C and
run postmaster. I supposed it uses C locale, but -d 5 shows in log:
DEBUG: /usr/bin/postmaster: PostmasterMain: initial environ dump:
.
.
.
DEBUG: LC_COLLATE=pl_PL.UTF-8
DEBUG: LC_CTYPE=pl_PL.UTF-8
DEBUG:
Hi,
Le jeudi 05 juillet 2007, Artur Rataj a écrit :
> Hello, I want to have pg use fast indexing for ~ operator. Is setting
> C locale for this is still necessary? If yes, is it enough to
> initdb/createdb with C locale? If it is not enough, why setting locale
> to C and starting postmaster still
Hello, I want to have pg use fast indexing for ~ operator. Is setting
C locale for this is still necessary? If yes, is it enough to
initdb/createdb with C locale? If it is not enough, why setting locale
to C and starting postmaster still gives other locale, for example,
pl_PL, in
postmaster log "i
