Received: from river-bank.demon.co.uk (river-bank.demon.co.uk [193.237.18.135]) by hub.org (8.8.8/8.7.5) with SMTP id OAA16131; Thu, 30 Apr 1998 14:37:22 -0400 (EDT) Received: from river-bank.demon.co.uk(really [192.168.0.1]) by river-bank.demon.co.uk via smtpd with esmtp id for ; Thu, 30 Apr 1998 19:33:43 +0100 (BST) (Smail-3.2 1996-Jul-4 #2 built 1997-Oct-12) Sender: phil Message-ID: <3548C407.7FDF45A0@river-bank.demon.co.uk> Date: Thu, 30 Apr 1998 18:33:43 +0000 From: Phil Thompson Organization: At home X-Mailer: Mozilla 4.04 [en] (X11; I; Linux 2.0.33 i586) MIME-Version: 1.0 To: Bruce Momjian CC: tgl@sss.pgh.pa.us, pgsql-hackers@postgreSQL.org, pgsql-interfaces@postgreSQL.org Subject: Re: [HACKERS] Revised proposal for libpq and FE/BE protocol changes References: <199804292303.TAA27447@candle.pha.pa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Bruce Momjian wrote: > > Either way, maintaining > > support for 1.0 is important as not all of us use libpq and we need time > > to catch up. Also we don't want to put barriers in the way of companies > > like Openlink who seem willing to provide support for PostgreSQL in > > commercial products. > > Yes, but there will be a month for people to get their third-part stuff > changed, and the changes are pretty straight-forward. Having support > for both in the backend/frontend is going to make that code more > difficult. I agree it will be easy enough for most of us, but may be less so for companies that traditionally don't release often. Although I don't use Openlink's software and can't comment on whether it's any good (or if anybody actually uses it), I take it as a compliment to PostgreSQL that a commercial organisation is willing to provide some support for it. Not maintaining backwards compatibility for at least some time isn't going to encourage them to continue that support. Phil