From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Tony Grant <tony(at)animaproductions(dot)com> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Re: A bug with pgsql 7.1/jdbc and non-ascii (8-bit) chars? |
Date: | 2001-05-04 16:40:26 |
Message-ID: | 25661.988994426@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-jdbc |
Tony Grant <tony(at)animaproductions(dot)com> writes:
> What kind of error message does "createdb -E LATIN1" give on a non
> MULTIBYTE backend?
$ createdb -E LATIN1 foo
/home/postgres/testversion/bin/createdb[143]: /home/postgres/testversion/bin/pg_encoding: not found.
createdb: "LATIN1" is not a valid encoding name
$
> 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...
But they *should not* need it, if they only want to use an 8-bit character
set. Locale support should be enough. Or so I would think, anyway.
I have to admit I have not looked very closely at the functionality
that's enabled by MULTIBYTE; is any of it really needed to deal with
LATINn character sets?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2001-05-04 16:48:58 | Re: Re: New Linux xfs/reiser file systems |
Previous Message | Bruce Momjian | 2001-05-04 16:36:23 | Re: Re: New Linux xfs/reiser file systems |
From | Date | Subject | |
---|---|---|---|
Next Message | Marko Kreen | 2001-05-04 17:26:48 | Re: Bug-report (was: JDBC driver in pgsql 7.1 build problem) |
Previous Message | Tony Grant | 2001-05-04 16:29:57 | Re: Re: A bug with pgsql 7.1/jdbc and non-ascii (8-bit) chars? |