X-Original-To: pgsql-hackers@postgresql.org Received: from spampd.localdomain (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 48F4C474E42; Thu, 10 Apr 2003 18:04:48 -0400 (EDT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id F2009475EFD; Thu, 10 Apr 2003 18:04:46 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.9/8.12.9) with ESMTP id h3AM4n2L007057; Thu, 10 Apr 2003 18:04:49 -0400 (EDT) To: Barry Lind Cc: pgsql-hackers@postgresql.org, pgsql-interfaces@postgresql.org Subject: Re: More thoughts about FE/BE protocol In-reply-to: <3E95DFDA.3010101@xythos.com> References: <10478.1049927451@sss.pgh.pa.us> <3E95A3CD.9080500@xythos.com> <5564.1049998513@sss.pgh.pa.us> <3E95DFDA.3010101@xythos.com> Comments: In-reply-to Barry Lind message dated "Thu, 10 Apr 2003 14:19:22 -0700" Date: Thu, 10 Apr 2003 18:04:48 -0400 Message-ID: <7056.1050012288@sss.pgh.pa.us> From: Tom Lane X-Spam-Status: No, hits=-32.5 required=5.0 tests=BAYES_01,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT, REFERENCES,REPLY_WITH_QUOTES autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) X-Archive-Number: 200304/341 X-Sequence-Number: 37831 Barry Lind writes: > This all sounds great. I am really looking to seeing all of this > implemented. Are you still on schedule for getting this into 7.4? I gotta get off my duff and get with it, but I still plan to do it. > And will there be time left for the clients to make the changes > necessary to use the new protocol? Well, that depends how long they take ;-) I had originally planned to do the error message revisions first, but I now think they should be last, or at least the long/tedious part of converting all the backend elog calls should be put off to last. That will provide an interval where all the protocol-level revisions are done and so people can hack on the clients in parallel with the backend work. I'll try to put out a protocol spec document first, which would give you something to shoot at, but I'm not really expecting anyone to work very hard on it until there's backend code to test against ... regards, tom lane