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 8E9DC474E4F for ; Fri, 21 Mar 2003 12:42:27 -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 h2LHgPub014031; Fri, 21 Mar 2003 12:42:25 -0500 (EST) To: Bruce Momjian Cc: Peter Eisentraut , Alvaro Herrera , PostgreSQL Development Subject: Re: [INTERFACES] Roadmap for FE/BE protocol redesign In-reply-to: <200303211714.h2LHE8J07989@candle.pha.pa.us> References: <200303211714.h2LHE8J07989@candle.pha.pa.us> Comments: In-reply-to Bruce Momjian message dated "Fri, 21 Mar 2003 12:14:08 -0500" Date: Fri, 21 Mar 2003 12:42:25 -0500 Message-ID: <14030.1048268545@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200303/928 X-Sequence-Number: 37174 Bruce Momjian writes: > Peter Eisentraut wrote: >> The standard only covers embedded C programs. Other interfaces that are >> covered by other standards require other settings. > My point was that _the_ standard requires autocommit off, not that > everyone is using autocommit off. Peter's point is good: the only interface that is actually subject to the part of the spec you are quoting is ecpg. It could reasonably be argued that libpq should only support autocommit-on, because that's the historical behavior that programs written atop libpq expect. The other client libraries have their own specs to adhere to. regards, tom lane