Re: initdb with lc-collate=C

Nope....  no clusters.  I never got past the initial install and configure.

All I did was install, initdb, alter a few things in postgresql.conf (nothing relating to locale) and pg_hba.conf,
startpostgres using the init script, and run the query to check the collation setting.  Nothing more. 

Scot Kreienkamp
Senior Systems Engineer
skreien@la-z-boy.com


-----Original Message-----
From: Adrian Klaver [mailto:adrian.klaver@gmail.com]
Sent: Monday, December 12, 2011 3:26 PM
To: Scot Kreienkamp
Cc: Postgres General (pgsql-general@postgresql.org)
Subject: Re: [GENERAL] initdb with lc-collate=C

On 12/12/2011 12:15 PM, Adrian Klaver wrote:
> 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@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?

Wrong question:( Read the above too quickly and did not pick up you
where getting the setting from pg_settings.

Try again.
Is there more than one database cluster on the machine and if so are you
sure you did the initdb on the same cluster as the select..?

>
>>
>> Thanks!
>>
>> Scot Kreienkamp
>>
>
>
>


--
Adrian Klaver
adrian.klaver@gmail.com
This message is intended only for the individual or entity to which it is addressed. It may contain privileged,
confidentialinformation which is exempt from disclosure under applicable laws. If you are not the intended recipient,
pleasenote that you are strictly prohibited from disseminating or distributing this information (other than to the
intendedrecipient) or copying this information. If you have received this communication in error, please notify us
immediatelyby e-mail or by telephone at the above number. Thank you.