From: kwiles81@earthlink.net
To: L J Bayuk <ljb220@mindspring.com>
Subject: Re: Can not connect with pgin.tcl
Date: Thu, 12 Feb 2004 09:27:15 -0600
User-Agent: KMail/1.5
Cc: pgsql-interfaces@postgresql.org
References: <200402112255.i1BMtOcO000225@mindspring.com>
In-Reply-To: <200402112255.i1BMtOcO000225@mindspring.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200402120927.15294.kwiles81@earthlink.net>

On Wednesday 11 February 2004 04:55 pm, L J Bayuk wrote:

Funny, after sent the email I upgraded to PostgreSQL 7.4.1but did not check 
pgin.tcl out until I read this message.

It works now, thank you.

I guess I missed that revision issue in the docs, sorry.

> kwiles81@earthlink.net wrote:
> > I get the messge saying that it is an unsupported frontend protocol.
> >
> > I am using the MD5 option in the pg_hba.conf file, is this my problem?
>
> Not the problem. MD5 option is good. Use it.
>
> > Or am I using an out of date version?  What I have is pgintcl-2.0b1.
>
> pgintcl-2.0 and up speak only to servers running PostgreSQL-7.4 and
> higher. If you are trying to talk to a PostgreSQL-7.3.x or lower
> server, you need to use the older pgintcl-1.5.0.
>
>  Server version:               Protocol:    pgintcl-1.5.0   pgintcl-2.0.x
>  ----------------              ---------    -------------   -------------
>  PostgreSQL-7.3.x and lower     V2             Yes           No
>  PostgreSQL-7.4 and higher      V3 or V2       Yes           Yes
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
>       subscribe-nomail command to majordomo@postgresql.org so that your
>       message can get through to the mailing list cleanly