Re: initdb problen

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: "Korea PostgreSQL Users' Group" <pgsql-kr(at)postgresql(dot)or(dot)kr>
Cc: Claudio Natoli <claudio(dot)natoli(at)memetrics(dot)com>, pgsql-hackers-win32(at)postgresql(dot)org
Subject: Re: initdb problen
Date: 2004-03-12 10:03:57
Message-ID: 40518B0D.1090208@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers-win32 pgsql-patches


the answer is very probably here:
http://archives.postgresql.org/pgsql-hackers-win32/2003-10/msg00024.php

I thought Bruce said he had this covered, but it hasn't been fixed. I
will prepare a patch in the next day or so if someone else doesn't beat
me to it.

cheers

andrew

Korea PostgreSQL Users' Group wrote:

>it works still problem.
>
>setlocale() function is not equivalent between unix and win32
>
>plz check.
>
>multibyte text is not sorted.
>
>
>----- Original Message -----
>From: "Claudio Natoli" <claudio(dot)natoli(at)memetrics(dot)com>
>To: "'Korea PostgreSQL Users' Group'" <pgsql-kr(at)postgresql(dot)or(dot)kr>; <pgsql-hackers-win32(at)postgresql(dot)org>
>Sent: Friday, March 12, 2004 5:04 PM
>Subject: RE: [pgsql-hackers-win32] initdb problen
>
>
>
>
>>What if you instead try:
>>
>>initdb --locale=C
>>
>>Looks like "--no-locale" is not "equivalent to --locale=C", at least under
>>win32.
>>
>>Cheers,
>>Claudio
>>
>>
>>
>>
>
>---------------------------(end of broadcast)---------------------------
>TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
>
>
>

In response to

Responses

Browse pgsql-hackers-win32 by date

  From Date Subject
Next Message Merlin Moncure 2004-03-12 12:56:27 Re: Thanks for the great work on the Win32 port
Previous Message Korea PostgreSQL Users' Group 2004-03-12 08:25:33 Re: initdb problen

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2004-03-12 13:55:53 Re: initdb problen
Previous Message Andrew Dunstan 2004-03-12 09:49:25 Re: defer statement logging until after parse