Tony Grant wrote:

> On 04 May 2001 11:40:48 -0400, Tom Lane wrote:
>> But a non-MULTIBYTE backend doesn't even have the concept of "setting
>> the encoding" --- it will always just report SQL_ASCII.
> What kind of error message does "createdb -E LATIN1" give on a non
> MULTIBYTE backend? 
> Maybe there needs to be a note somewhere informing people from Europe
> that they too need MULTIBYTE as an option at compile time. i.e. In a
> bright yellow box in the HTML docs...
> And in the Reference manual and man pages the -E option for createdb
> needs a note to specify that it applies to MULTIBYTE backends only. 
> Cheers
> Tony Grant
The errors you get are:
from createdb-

$ createdb -E LATIN1 testdb
/usr/local/pgsql/bin/createdb: /usr/local/pgsql/bin/pg_encoding: No such 
file or directory
createdb: "LATIN1" is not a valid encoding name

and from psql-

template1=# create database testdb with encoding = 'LATIN1';
ERROR:  Multi-byte support is not enabled


---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

Reply via email to