Re: Problem in order by - Mailing list pgsql-admin

From Reuly Bússolo Mendes
Subject Re: Problem in order by
Date
Msg-id 032e01c53f6d$6f6a74c0$5c00a8c0@intranet.tecmicro.com.br
Whole thread Raw
In response to Problem in order by  (Reuly Bússolo Mendes <reuly@terra.com.br>)
Responses Re: Problem in order by
List pgsql-admin
The command's return
teste=# show LC_COLLATE;
ERROR:  Option 'lc_collate' is not recognized

I remade the process of yesterday (dropdb and move directory) and added in
initdb the option --lc_collate=C without taking off -- locale=C, executed
but it does not appear in postgresql.conf and the problem continues.

it forgives me for my English

Tks
Reuly



----- Original Message -----
From: "Stephan Szabo" <sszabo@megazone.bigpanda.com>
To: "Reuly Bússolo Mendes" <reuly@terra.com.br>
Cc: <pgsql-admin@postgresql.org>
Sent: Tuesday, April 12, 2005 10:58 AM
Subject: Re: [ADMIN] Problem in order by


On Mon, 11 Apr 2005, [iso-8859-1] Reuly Bússolo Mendes wrote:

> Hi Stephan, tks
>
> I drop database and move directory data to data01.
> I already executed "initdb --locale=C" and the file postgresql.conf change
> to LC_MESSAGES, LC_MONETARY, LC_NUMERIC and LC_TIME = 'C', but the problem
> persist.


I think LC_COLLATE would be the one that is the issue, but --locale=C
should have done it I think.  To be sure, what does "show LC_COLLATE;"
give on the database that has the problem?


---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend



--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.9.7 - Release Date: 12/4/2005



pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: upper() with LATIN1 problem
Next
From: Marcin Giedz
Date:
Subject: pg_temp_xxx schemas