RE: client_encoding is WIN1252 on ErrorMessage at the StartupMessage

I'm developing the wire protocol on programmable logic controller (PLC) to communicate with the backend server.
The PostgreSQL server run on Windows 10 French Canadian.
The client_encoding on the server and database encoding is UTF8.
The collation and character type are French_Canada.1252.
The PLC is UTF8.
After TCP/IP connection, the PLC send the "StartupMessage" but receive an "ErrorResponse" because no access right.
The error message is in WIN1252 not UTF8!
If grant connect access to user and get data from database all is UTF8!
Is it a bug or bad setup?

Regards,

Jean-Yves Garneau <Jean-Yves(dot)Garneau(at)invest-quebec(dot)com> writes:
> I'm developing the wire protocol on programmable logic controller (PLC) to communicate with the backend server.
> The PostgreSQL server run on Windows 10 French Canadian.
> The client_encoding on the server and database encoding is UTF8.
> The collation and character type are French_Canada.1252.
> The PLC is UTF8.
> After TCP/IP connection, the PLC send the "StartupMessage" but receive an "ErrorResponse" because no access right.
> The error message is in WIN1252 not UTF8!
> If grant connect access to user and get data from database all is UTF8!
> Is it a bug or bad setup?

Bad setup, I'd say. If you have a connection failure before the backend
has joined a particular database, it won't have adopted any database-level
encoding or locale; moreover I don't think it's capable of doing encoding
translation at that point. So any such messages are going to be sent with
encoding matching the postmaster process's native locale, which you seem
to have chosen more or less at random. If you have a global expectation
about what encoding to use, best make the postmaster's startup locale
settings match that.

regards, tom lane

Dear Tom,

For me UTF8 is the choice and I used :
* client_encoding = UTF8
* server_encoding = UTF8

Is there another encoding variable to setup?

Regards,
Jean-Yves Garneau

Jean-Yves Garneau <Jean-Yves(dot)Garneau(at)invest-quebec(dot)com> writes:
> Dear Tom,
> For me UTF8 is the choice and I used :
> * client_encoding = UTF8
> * server_encoding = UTF8

> Is there another encoding variable to setup?

What's lc_messages set to (in postgresql.conf)?

regards, tom lane

French_Canada.1252

Jean-Yves Garneau <Jean-Yves(dot)Garneau(at)invest-quebec(dot)com> writes:
> French_Canada.1252

That's where your WIN1252 is coming from, then. You need to make
that be something utf-8-based.

regards, tom lane

I replaced the lc_messages to 'UTF8' but received the error response in English.
I replaced the lc_messages to 'French_Canada.UTF8' but received the error response in 1252.

Jean-Yves Garneau <Jean-Yves(dot)Garneau(at)invest-quebec(dot)com> writes:
> I replaced the lc_messages to 'UTF8' but received the error response in English.
> I replaced the lc_messages to 'French_Canada.UTF8' but received the error response in 1252.

Sorry, I don't know much about how Windows locales work. You may
have to mess with something like the code page environment in which
the postmaster is started.

regards, tom lane

Thank you Tom.