From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Don Isgitt <djisgitt(at)soundenergy(dot)com> |
Cc: | pgsql-general newsgroup <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pgaccess error message |
Date: | 2002-08-15 15:52:35 |
Message-ID: | 23798.1029426755@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Don Isgitt <djisgitt(at)soundenergy(dot)com> writes:
> [ pgaccess fails with ]
> PostgreSQL error message:Connection to database failed
> ERROR: Client encoding UNICODE is not supported
It looks like pgaccess is trying to use MULTIBYTE support, and your
server wasn't compiled with MULTIBYTE.
I think this shouldn't happen if pgaccess was also built without
multibyte support ... but I haven't looked at the tcl/tk interfaces
in awhile. There may be some unintended dependency in there. Or
maybe pgaccess is just picking up a stray libpgtcl (from somewhere
else on your system) that was built with multibyte support.
You can try to track down where the assumption of multibyte support is
coming in on the client side, or you can take the easy way out and
rebuild your server with multibyte support ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Linn Kubler | 2002-08-15 16:04:05 | Re: Problem with Now()? |
Previous Message | Justin Clift | 2002-08-15 15:52:11 | Re: Why choose PostreSQL and not MySQL or Oracle!! |