is win1250 supported encoding for PG7.5?

[Pavel Stehule]

Hello

I have only one questions. I am testing PostgreSQL for windows.
All look well, but I can't set database encoding win1250. Its can be
problem, because win1250 is often used encoding on win32 platform in our
area. (PG7.5 don't support win1250 encoding on linux too).

Administrator@NEMESIS /usr/local/pgsql/lib
$ ../bin/createdb.exe -E win1250 aaa
createdb.exe: database creation failed: ERROR: win1250 is not a valid
encoding name

I can set win1250 for client_encoding without problem. Its problem in my
configuration or it's feature :-).

Thank You
Pavel Stehule


---------------------------(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

[Karel Zak]

On Mon, Jun 28, 2004 at 01:29:34PM +0200, Pavel Stehule wrote:

I have only one questions. I am testing PostgreSQL for windows.
All look well, but I can't set database encoding win1250. Its can be
problem, because win1250 is often used encoding on win32 platform in our
area. (PG7.5 don't support win1250 encoding on linux too).

Administrator@NEMESIS /usr/local/pgsql/lib
$ ../bin/createdb.exe -E win1250 aaa
createdb.exe: database creation failed: ERROR: win1250 is not a valid
encoding name
Shift JIS (Winindows-932)
Big5 (Windows-950)
GBK (Windows-936)
UHC (Windows-949)
windows-1250
PG_GB18030

are client encodings only. You can't create DB in these encodings. I'm
not sure if this behaviour is described in PostgreSQL's docs.

For details see include/mb/pg_wchar.h
I can set win1250 for client_encoding without problem. Its problem in my
configuration or it's feature :-).

That's right, it's feature. I agree that it's a little funny that you
can't use native windows encoding in the native windows PostgreSQL port
:-)

Karel

--
Karel Zak <za***@zf.jcu.cz>
http://home.zf.jcu.cz/~zakkr/

---------------------------(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