Re: encoding of PostgreSQL messages - Mailing list pgsql-general

Hi.

Sorry very late reaction.
I desire problem solution.Therefore, one evidence....

I tried jdbc program.
http://winpg.jp/~saito/pg_work/LC_MESSAGE_CHECK/connect_problem/jdbctestx.java
C:\home\HIROSHI>java jdbctestx
org.postgresql.util.PSQLException: FATAL: ???[??"postgres"??????????????
        at org.postgresql.core.v3.ConnectionFactoryImpl.readStartupMessages(Conn
ectionFactoryImpl.java:444)
        at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(Conne
ctionFactoryImpl.java:99)
        at org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactor
y.java:66)
        at org.postgresql.jdbc2.AbstractJdbc2Connection.<init>(AbstractJdbc2Conn
ection.java:124)
        at org.postgresql.jdbc2.Jdbc2Connection.<init>(Jdbc2Connection.java:24)
        at org.postgresql.Driver.makeConnection(Driver.java:386)
        at org.postgresql.Driver.connect(Driver.java:260)
        at java.sql.DriverManager.getConnection(Unknown Source)
        at java.sql.DriverManager.getConnection(Unknown Source)
        at jdbctestx.main(jdbctestx.java:21)

Then, server log is this.
http://winpg.jp/~saito/pg_work/LC_MESSAGE_CHECK/connect_problem/server.log

Regards,
Hiroshi Saito

----- Original Message -----
From: "Hiroshi Inoue" <inoue@tpf.co.jp>


> Tom Lane wrote:
>> Peter Eisentraut <peter_e@gmx.net> writes:
>>> Bruce Momjian wrote:
>>>> Can someone comment on this?
>>
>>> Looks like a horrible hack to me.  Recoding stuff to the client encoding
>>> in the server outside the existing recoding mechanism looks pretty evil
>>> to me.  Plus, it does not address the problem of what happens to
>>> messages sent before this, it just moves the point of "before" a bit
>>> earlier for some special cases.
>>
>>> I think we have discussed more proper solutions earlier in this thread.
>>>   IMO the best approach would be for the client to include the client
>>> encoding in the startup package.
>>
>> Huh?  Clients already do that (or at least some are capable of it,
>> including libpq).
>
> Yes the psqlodbc driver has done it because protocol 3 allowed it
> from the first.
>
>> The hard problems are (1) there's still a "before",
>
> Yes but isn't it an improvement that properly localized password error
> or no database error etc can be seen? Currently I see unreadable
> error messages for those cases via psqlodbc driver.  The attatched
> patch in my previous posting is an example to solve the problem.
>
> regards,
> Hirosh Inoue
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general