Tom Lane wrote:
Palle Girgensohn <[EMAIL PROTECTED]> writes:
hmm... I think I might have made a false assumption that the locale string would contain the character encoding.
You certainly cannot assume that. Would that it were so easy to find out the character set for a locale :-(.
There's some code in initdb that you might emulate, though I can't say that I trust it a whole lot.
Me either. On FC3 I saw this the other day, haven't had time to dig into what's going on:
[andrew inst]$ echo $LANG en_US.UTF-8 [andrew inst]$ bin/initdb floobl The files belonging to this database system will be owned by user "andrew". This user must also own the server process.
The database cluster will be initialized with locale en_US.UTF-8. initdb: could not find suitable encoding for locale "en_US.UTF-8" Rerun initdb with the -E option. Try "initdb --help" for more information.
cheers
andrew
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
