Home > Archive > PostgreSQL Bugs > December 2005 > BUG #2110: initdb set wrong default encoding









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author BUG #2110: initdb set wrong default encoding
Alexei

2005-12-13, 8:25 pm


The following bug has been logged online:

Bug reference: 2110
Logged by: Alexei
Email address: kaaos@land.ru
PostgreSQL version: 8.1.1
Operating system: Window XP SP2
Description: initdb set wrong default encoding
Details:

Good day!
I run initdb with --encoding=WIN1251 parameter, but
then 'psql -l' show that encoding of 'template{0,1}'
and 'postgres' databases is KOI8-R.

New databases created with KOI8-R encoding also,
unless specified by 'ENCODING' keyword, or '--encoding'
parameter.

During run of initdb no warning or error messages
printed.

It seems, that actually the encoding of 'template{0,1}' and 'postgres'
databases is valid (CP1251):
query "select '№'" print '№'. (№ - is a symbol
present in CP1251 at code 0x00b9 and not present in KOI8-R)

But in newly created database the same query print empty space (as in KOI8-R
database), and 'psql -l' show, that ALL databases have KOI8-R encoding.

Thank you and sorry for my English.

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Sponsored Links





Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive | Programming forum archive

Copyright 2008 droptable.com