Thread: error ' Client encoding Mismatch' with Version 8.1.4

error ' Client encoding Mismatch' with Version 8.1.4

From
"Ashutosh Kumar S-TLS,Chennai"
Date:
Hi,

=20

I am using  Postgres Version 8.1.4.

I installed it using UTF8 encoding. It was successfully installed. I
confirmed the same using "SHOW server_encoding" command in pgAdmin III
Query.=20

=20

Problem is whenever I am trying to open the database through ODBC
connection it throws an error 'Client encoding mismatch'. ( I am able to
run any command from pgAdmin III Query tester.

Seeking help on the same. I read on few blogs for the same. They say
UTF8 support in Version 8.1 is problematic.=20

=20

Thanks and Regards,

Ashutosh=20=20



DISCLAIMER:
---------------------------------------------------------------------------=
--------------------------------------------

The contents of this e-mail and any attachment(s) are confidential and inte=
nded for the named recipient(s) only.
It shall not attach any liability on the originator or HCL or its affiliate=
s. Any views or opinions presented in=20
this email are solely those of the author and may not necessarily reflect t=
he opinions of HCL or its affiliates.
Any form of reproduction, dissemination, copying, disclosure, modification,=
 distribution and / or publication of=20
this message without the prior written consent of the author of this e-mail=
 is strictly prohibited. If you have
received this email in error please delete it and notify the sender immedia=
tely. Before opening any mail and=20
attachments please check them for viruses and defect.

---------------------------------------------------------------------------=
--------------------------------------------=

Re: error ' Client encoding Mismatch' with Version 8.1.4

From
Tom Lane
Date:
"Ashutosh Kumar S-TLS,Chennai" <ashutoshks@hcl.in> writes:
> Problem is whenever I am trying to open the database through ODBC
> connection it throws an error 'Client encoding mismatch'.

That phrase occurs noplace in Postgres 8.1, so the error must be coming
from something on the client side.  We can't really help you here ---
you need to find out which bit of software is throwing the error and
ask its authors what is the cause.

            regards, tom lane

Re: error ' Client encoding Mismatch' with Version 8.1.4

From
"Ashutosh Kumar S-TLS,Chennai"
Date:
Hi all,

I tried to look into the problem, still unable to solve the problem.

Problem details:

We have a custom application which installs Postgres 8.1.4. It provides
option for selection of encoding.

Below is the line which does the same based on the encoding selection:

"

msiexec /i postgresql-8.1-int.msi /qn -l  %LogFile%
ADDLOCAL=3Dserver,psql,pgadmin INTERNALLAUNCH=3D1 DOSERVICE=3D1 DOINITDB=3D1
SERVICEDOMAIN=3D"%COMPUTERNAME%" SERVICEACCOUNT=3D"postgres"
SERVICEPASSWORD=3D"Password1*2*3"  SUPERPASSWORD=3D"postgres"
CREATESERVICEUSER=3D1 ENCODING=3D%Lang% LISTENPORT=3D7432 PERMITREMOTE=3D1
NOSHORTCUTS=3D1 BASEDIR=3D%JM_ROOT_WIN%\StdyDb
DATADIR=3D%JM_ROOT_WIN%\StdyDb\data

"

Where "Lang" is the selection done by user.

=20

I changed it to ENCODING=3D"UTF8" installation in UTF8 format.

=20

I installed the Postgres 8.1.4 version with UTF8 as encoding. This works
properly when my regional settings are Japanese but the same
installation fails as soon as I change my regional settings to Greek.
When I try to connect to the database with Greek regional settings it
throws the error "Client Encoding mismatch".=20

=20

I feel there is some setting done at the installation time which makes
it work correctly in Japanese regional language settings only. Hence it
fails when I change them to Greek.

What can be the cause for this behavior? Do I need to change some
settings on cygwin or pgaccess side at installation time?

I even tried changing the encoding for database to Unicode still the
same error. (createdb -E UTF8 Xyz)=20

=20

=20

Note:-

I have even tried with direct installation of Postgres version 8.1.4. It
behaves in the same way as our Custom installer is behaving. It seems
there is problem in the version 8.1.4 itself.

Tom,

I think the error is thrown from the Postgres side only. I am getting
the same error while working with direct installer of Postgres. I get
this error with Greek and Thai regional language settings, not with
Japanese.=20

=20

Please help me on the same.

=20

=20

=20

Regards,

Ashutosh

=20

-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]=20
Sent: Thursday, June 26, 2008 8:29 PM
To: Ashutosh Kumar S-TLS,Chennai
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] error ' Client encoding Mismatch' with Version 8.1.4


=20

"Ashutosh Kumar S-TLS,Chennai" <ashutoshks@hcl.in> writes:

> Problem is whenever I am trying to open the database through ODBC

> connection it throws an error 'Client encoding mismatch'.

=20

That phrase occurs noplace in Postgres 8.1, so the error must be coming

from something on the client side.  We can't really help you here ---

you need to find out which bit of software is throwing the error and

ask its authors what is the cause.

=20

                  regards, tom lane



DISCLAIMER:
---------------------------------------------------------------------------=
--------------------------------------------

The contents of this e-mail and any attachment(s) are confidential and inte=
nded for the named recipient(s) only.
It shall not attach any liability on the originator or HCL or its affiliate=
s. Any views or opinions presented in=20
this email are solely those of the author and may not necessarily reflect t=
he opinions of HCL or its affiliates.
Any form of reproduction, dissemination, copying, disclosure, modification,=
 distribution and / or publication of=20
this message without the prior written consent of the author of this e-mail=
 is strictly prohibited. If you have
received this email in error please delete it and notify the sender immedia=
tely. Before opening any mail and=20
attachments please check them for viruses and defect.

---------------------------------------------------------------------------=
--------------------------------------------=