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 0BA6A475FC6 for ; Mon, 17 Mar 2003 20:48:40 -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 h2I1mfub013208; Mon, 17 Mar 2003 20:48:41 -0500 (EST) To: Peter Eisentraut Cc: PostgreSQL Development Subject: Re: [INTERFACES] Roadmap for FE/BE protocol redesign In-reply-to: References: Comments: In-reply-to Peter Eisentraut message dated "Tue, 18 Mar 2003 01:22:55 +0100" Date: Mon, 17 Mar 2003 20:48:41 -0500 Message-ID: <13207.1047952121@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200303/691 X-Sequence-Number: 36937 Peter Eisentraut writes: > Tom Lane writes: >> * Backend's ReadyForQuery message (Z message) should carry an indication >> of current transaction status (idle/in transaction/in aborted transaction) >> so that frontend need not guess at state. Perhaps also indicate >> autocommit status. > If we do this, could we get rid of the messy autocommit GUC option and > handle autocommit in the client? Hmm ... that's a thought ... not very backwards-compatible with 7.3, but I think I like it better than continuing on with the GUC option. As you say, that path is looking messier all the time. Comments anyone? regards, tom lane