Subject: pkg/19818: pgaccess cannot connect to non-ASCII database
To: None <gnats-bugs@gnats.netbsd.org>
From: None <mlelstv@serpens.de>
List: netbsd-bugs
Date: 01/12/2003 18:28:55
>Number: 19818
>Category: pkg
>Synopsis: pgaccess cannot connect to non-ASCII database
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: pkg-manager
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sun Jan 12 09:30:01 PST 2003
>Closed-Date:
>Last-Modified:
>Originator: Michael van Elst
>Release: NetBSD 1.6_STABLE
>Organization:
none
>Environment:
System: NetBSD pepew 1.6_STABLE NetBSD 1.6_STABLE (PEPEW) #26: Mon Jan 6 23:20:56 MET 2003 src@pepew:/amd/fud/d/0/src/sys/arch/i386/compile/PEPEW i386
Architecture: i386
Machine: i386
>Description:
postgresql allows to create databases with a specific locale, a client
can then translate between the character set on the client and that
stored in the database.
Since postgresql 7.3.1 pgaccess fails to connect to such a database with
an error message:
| PostgreSQL error message:Connection to database failed
| ERROR: Conversion between UNICODE and LATIN1 is not supported.
and provides help
[...]
| 3. If it's a UNICODE error, you will need to recompile PostgreSQL from
source. Some linux distros include a buggy libpgtcl.so that
needs replacing.
>How-To-Repeat:
Create a database in PostgreSQL using something like
CREATE DATABASE foo WITH ENCODING = 'LATIN1' ;
then try to connect to the database using pgaccess.
I have tested with the old pgaccess-0.98.7 and the new 0.98.8
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: