And here is pgadmin3 log file:
2003-11-26 19:25:37 INFO : Destroying a connect dialogue
2003-11-26 19:25:37 STATUS : Connecting to database...
2003-11-26 19:25:37 INFO : Creating pgConn object
2003-11-26 19:25:37 INFO : Server name: 192.169.0.254 (resolved to: 192.169.0.254)
2003-11-26 19:25:37 INFO : Opening connection with connection string: hostaddr='192.169.0.254' dbname='template1' user='xxx' password='yyy' port=5432
2003-11-26 19:25:37 QUERY : Set query (192.169.0.254:5432): SELECT pg_encoding_to_char(encoding) AS encoding, datlastsysoid
FROM pg_database WHERE datname='template1'
2003-11-26 19:25:37 INFO : Creating pgSet object
2003-11-26 19:25:37 INFO : Setting client_encoding to 'UNICODE'
2003-11-26 19:25:37 ERROR : ?????????????????????????????????????????????????????????????????????????????????????????????????????????T
Sorry to come back on this so late.
Seems as if a message box is to be displayed, but the error string is corrupted, so pango will hickup.
The message originates from the pgConn ctor (line 163), where the conversion from UTF8 to wchar_t is missing.
Corrected in cvs, can you verify that your problem's gone?
Regards, Andreas
---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives?
http://archives.postgresql.org
