I believe this is a locale issue, where the server and client are in different 'Postgres' locales. Unfortunately I don't know how to fix this. You might try manually setting the appropriate env. vars.
-derek John Abreau <[EMAIL PROTECTED]> writes: > I've been using pgaccess through an ssh tunnel to maintain a remote > postgres database. Since I upgraded to Redhat 7.3, pgaccess no longer > works; when I try to connect, it gives the following error: > > PostgreSQL error message:Connection to database failed > ERROR: Conversion between UNICODE and SQL_ASCII is not supported > > I've had no luck tracking down a fix for this. Has anyone else run into > this error before, and if so, how did you fix it? > > Thanks. > > > -- > John Abreau / Executive Director, Boston Linux & Unix > ICQ 28611923 / AIM abreauj / JABBER [EMAIL PROTECTED] / YAHOO abreauj > Email [EMAIL PROTECTED] / WWW http://www.abreau.net / PGP-Key-ID 0xD5C7B5D9 > PGP-Key-Fingerprint 72 FB 39 4F 3C 3B D6 5B E0 C8 5A 6E F1 2C BE 99 > > "The early bird catches the worm, but the second mouse gets the cheese." > > -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH [EMAIL PROTECTED] PGP key available ***************************************************************** To unsubscribe from this list, send mail to [EMAIL PROTECTED] with the text 'unsubscribe gnhlug' in the message body. *****************************************************************
