Send client-encoding in startup packet not SET

[ringerc]

It looks like we may have an issue with client-encoding and pre-auth errors. Per:

http://stackoverflow.com/q/24496757/398670

I'll look into this when time permits, just noting it here for now.

[davecramer]

From what I can see the encoding is set before the auth

https://github.com/pgjdbc/pgjdbc/blob/master/org/postgresql/core/v3/ConnectionFactoryImpl.java#L170

[lufte]

Hi. Having @ringerc 's answer in the stackoverflow question I did a little test and he seems to be right.

1. Try to connect with wrong password and you get the message: FATAL: la autentificaci��n password fall�� para el usuario ��postgres��.
2. Connect with correct password, send the query "SELECT 1/0" and you get the message: "ERROR: división por cero". Note the "ó" character now correctly encoded.

[davecramer]

Hmmm strange as we do set the encoding before the authentication. Unless
this is a backend problem

Dave Cramer

On 1 July 2014 17:29, Javier Ayres notifications@github.com wrote:

Hi. Having @ringerc https://github.com/ringerc 's answer in the
stackoverflow question I did a little test and he seems to be right.

1. Try to connect with wrong password and you get the message: FATAL: la
   autentificaci��n password fall�� para el usuario ��postgres��.
2. Connect with correct password, send the query "SELECT 1/0" and you get
   the message: "ERROR: división por cero". Note the "ó" character now
   correctly encoded.

—
Reply to this email directly or view it on GitHub
#165 (comment).