Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [206.210.65.6])
	by hub.org (8.9.1/8.9.1) with ESMTP id MAA01454
	for <pgsql-interfaces@postgreSQL.org>;
	Tue, 29 Dec 1998 12:10:53 -0500 (EST)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id MAA29778;
	Tue, 29 Dec 1998 12:09:38 -0500 (EST)
To: Stan Brown <stanb@awod.com>
cc: PostgreSQL Interfaces <pgsql-interfaces@postgreSQL.org>
Subject: Re: [INTERFACES] Can;t connect to db with pgaccess 
In-reply-to: Your message of Tue, 29 Dec 1998 09:52:58 +0200
	<36888A5A.CD1CCBA8@flex.ro>
Date: Tue, 29 Dec 1998 12:09:38 -0500
Message-ID: <29776.914951378@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Constantin Teodorescu <teo@flex.ro> writes:
> Stan Brown wrote:
>> Downloaded the latest pgacess. Looks pretty neat. Unfortunatley it will
>> not connect to my 6.3 database.

> PgAccess 0.93 will work fine on PostgreSQL 6.4 and higher.
> Due to some enhancements made in libpgtcl, there is another option to
> pg_result (-error) that does not exist in PosgreSQL 6.3.x

I think Stan's problem is at a lower level than that: 6.4 libpq will not
talk to a pre-6.4 server, period.  (It wants the 2.0 version of the
FE-to-BE protocol, which the older servers don't offer.  The other way
around, new server and old client, is no problem.)

6.4 libpgtcl won't work without 6.4 libpq, either.

You could put the PgAccess 0.93 Tcl code atop a 6.3.x libpgtcl and
libpq, and then it'd talk to older servers.  I dunno whether the
"-error" change that Constantin mentions is the only change that
would be needed in the Tcl code.

It'd probably be a more profitable use of your time to upgrade to
a 6.4(.1) server.  My experience is that 6.4 is a good deal more
stable than 6.3.x...

			regards, tom lane