Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [206.210.65.6]) by hub.org
	(8.8.8/8.7.5) with ESMTP id KAA13867;
	Fri, 22 May 1998 10:49:43 -0400 (EDT)
Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.sss.pgh.pa.us (8.8.5/8.8.5) with ESMTP id KAA24746;
	Fri, 22 May 1998 10:49:42 -0400 (EDT)
To: pgsql-hackers@postgreSQL.org, pgsql-interfaces@postgreSQL.org
Subject: Re: [HACKERS] Revised proposal for libpq and FE/BE protocol changes 
In-reply-to: Your message of Fri, 22 May 1998 00:00:02 -0700 (PDT)
	<9805220700.AA11579@hawk.illustra.com>
Date: Fri, 22 May 1998 10:49:41 -0400
Message-ID: <24744.895848581@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

dg@illustra.com (David Gould) writes:
> I know this is old old discussion, so "shut up, we're done with it" is a
> fine answer...
> But, I think maintaining compatibility with 1.0 is important. 

We did maintain compatibility, in that the server will still talk to
a client that identifies itself as 1.0 in the initial handshake.
(Kudos to whoever had the foresight to put a protocol version number
in the startup message, BTW.)

As things are currently set up, however, a new compilation of libpq
will only know how to talk protocol 2.0, so it cannot be used to
talk to an old server.  Are you concerned about that?  I don't see
any easy way around it...

			regards, tom lane