Re: initdb with lc-collate=C

From: Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>
To: Scot Kreienkamp <SKreien(at)la-z-boy(dot)com>
Cc: "Postgres General (pgsql-general(at)postgresql(dot)org)" <pgsql-general(at)postgresql(dot)org>
Subject: Re: initdb with lc-collate=C
Date: 2011-12-12 20:15:38
Message-ID: 4EE660EA.6010606@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 12/12/2011 10:49 AM, Scot Kreienkamp wrote:
> Hey guys,
>
> In PG 8.x, when I did an initdb with --lc-collate=c it was always
> effective in setting it server wide so it would apply to all databases.
> However, in 9.1.2, when I run initdb like so: /etc/init.d/postgresql-9.1
> initdb --lc-collate=C, it doesn't seem to have any effect.
>
> [root(at)dvrv5030 9.1]# psql -U postgres -Aqtc "select setting from
> pg_settings where name='lc_collate'"
>
> en_US.UTF-8
>
> Not sure why the difference in behavior. Our application depends on
> collation being set to C. I can create the individual database with that
> option, but why won't it stick setting it server-wide with initdb?

Databases are created using template1 as the default template. Did the
lc_collate get changed for template1?

>
> Thanks!
>
> Scot Kreienkamp
>

--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2011-12-12 20:26:11 Re: initdb with lc-collate=C
Previous Message Andreas Brandl 2011-12-12 19:13:42 Re: Statistics mismatch between n_live_tup and actual row count