Skip site navigation (1) Skip section navigation (2)

Re: Show encoding in initdb messages

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Show encoding in initdb messages
Date: 2004-06-21 16:22:19
Message-ID: 40D70B3B.3060804@dunslane.net (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Tom Lane wrote:

>Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
>  
>
>>But the answer space is infinite:
>>    
>>
>
>  
>
>>$ LANG=C locale charmap
>>ANSI_X3.4-1968
>>    
>>
>
>Right, the hard part is mapping whatever weird string "locale charmap"
>chooses to return into one of the encodings our code knows about.
>
>HPUX seems to be just arbitrarily bizarre:
>
>$ LC_ALL=en_US.iso88591 locale charmap
>"iso88591.cm"
>$ LC_ALL=C.utf8 locale charmap
>"utf8.cm"
>$
>
>As near as I can tell, the .cm is present in all the possible results;
>and why the quotes?
>  
>


>  
>
>>I suspect Japanese users will also have a problem with this mechanism, 
>>but at least we could keep -E to override the automatic selection.
>>    
>>
>
>Perhaps we could try to derive a setting from locale charmap, but barf
>and require explicit -E if we can't recognize it?
>
>  
>

Sounds like an excellent plan, at least for platforms that have such a 
command. Windows does not appear to :-(. Are there other *nixes that 
also lack it, or that also produce bizarre results like PH-UX?

cheers

andrew

In response to

Responses

pgsql-hackers by date

Next:From: Greg StarkDate: 2004-06-21 17:31:57
Subject: Re: placeholder syntax
Previous:From: Tom LaneDate: 2004-06-21 16:03:38
Subject: Re: Show encoding in initdb messages

pgsql-patches by date

Next:From: Alvaro HerreraDate: 2004-06-22 02:01:05
Subject: Re: nested xacts and phantom Xids
Previous:From: Tom LaneDate: 2004-06-21 16:03:38
Subject: Re: Show encoding in initdb messages

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group