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 LAA00875 for ; Wed, 20 Jan 1999 11:50:18 -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 LAA06747; Wed, 20 Jan 1999 11:49:41 -0500 (EST) To: Simon Evans cc: pgsql-interfaces@postgreSQL.org Subject: Re: [INTERFACES] Newer frontend talking to older backend In-reply-to: Your message of Wed, 20 Jan 1999 09:31:56 +0000 Date: Wed, 20 Jan 1999 11:49:41 -0500 Message-ID: <6745.916850981@sss.pgh.pa.us> From: Tom Lane Simon Evans writes: > I have a webserver which has to talk to various PostgeSQL backends > (some are 6.3.2 and some 6.4.2). I have the libpg from 6.4.2 on the > webserver and it talks fine to the 6.4.2 backends however I get > `Unsupported frontend protocol` when talking to the 6.3.2 backends. > Is there a way to get libpq to talk the 6.3.2 protocol or is the > only solution to upgrade all the backends to 6.4.2? No go, I'm afraid. You can put the client back to 6.3.2 and it should talk to both old and new servers; or you can upgrade all your servers. But a new client won't talk to old servers. Sorry. (My advice would be to upgrade the servers. 6.4 has been notably more stable in production use for my company than 6.3.2 was ...) regards, tom lane