X-Original-To: pgsql-hackers@postgresql.org Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 68C3E4760E3; Mon, 10 Mar 2003 14:30:22 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.8/8.12.8) with ESMTP id h2AJUMub019295; Mon, 10 Mar 2003 14:30:22 -0500 (EST) To: Rod Taylor Cc: PostgreSQL Development , pgsql-interfaces@postgresql.org Subject: Re: Roadmap for FE/BE protocol redesign In-reply-to: <1047324016.99075.31.camel@jester> References: <19041.1047322279@sss.pgh.pa.us> <1047324016.99075.31.camel@jester> Comments: In-reply-to Rod Taylor message dated "10 Mar 2003 14:20:17 -0500" Date: Mon, 10 Mar 2003 14:30:22 -0500 Message-ID: <19294.1047324622@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200303/372 X-Sequence-Number: 36618 Rod Taylor writes: > I'd be tempted to make a startup packet that will allow libpq to revert > back to old protocols easily enough for the future so that we can do=20 > incremental changes to the protocol. We already have that: you send a startup packet with a version less than the latest, and the backend speaks that version to you. One thing I want to do though is relax the protocol-level constraints on certain message contents: for example, if ErrorMessage becomes a collection of labeled fields, it should be possible to add new field types without calling it a protocol revision. The protocol need only specify "ignore any fields whose label you do not recognize". regards, tom lane