X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id EDA0BD1B579 for ; Mon, 17 Nov 2003 10:17:07 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 30431-08 for ; Mon, 17 Nov 2003 06:16:38 -0400 (AST) Received: from fuji.krosing.net (217-159-136-226-dsl.kt.estpak.ee [217.159.136.226]) by svr1.postgresql.org (Postfix) with ESMTP id 775F0D1B584 for ; Mon, 17 Nov 2003 06:16:19 -0400 (AST) Received: from fuji.krosing.net (localhost.localdomain [127.0.0.1]) by fuji.krosing.net (8.12.8/8.12.8) with ESMTP id hAHAGDJC020262; Mon, 17 Nov 2003 12:16:13 +0200 Received: (from hannu@localhost) by fuji.krosing.net (8.12.8/8.12.8/Submit) id hAHAG6M9020260; Mon, 17 Nov 2003 12:16:06 +0200 X-Authentication-Warning: fuji.krosing.net: hannu set sender to hannu@tm.ee using -f Subject: Re: start of transaction (was: Re: [PERFORM] Help with From: Hannu Krosing To: Tom Lane Cc: Neil Conway , Will LaShell , Christopher Browne , "pgsql-hackers@postgresql.org" In-Reply-To: <3798.1069027704@sss.pgh.pa.us> References: <200311141251.38786.mallah@trade-india.com> <1068831807.2540.44.camel@fuji.krosing.net> <3FB52FA7.8060508@lashell.net> <4987.1068842326@sss.pgh.pa.us> <87isllbcys.fsf@mailbox.samurai.com> <26338.1068996163@sss.pgh.pa.us> <87n0avaonp.fsf@mailbox.samurai.com> <3798.1069027704@sss.pgh.pa.us> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1069064165.20092.20.camel@fuji.krosing.net> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Mon, 17 Nov 2003 12:16:06 +0200 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200311/862 X-Sequence-Number: 47150 Tom Lane kirjutas E, 17.11.2003 kell 02:08: > Neil Conway writes: > > Hmmm... I agree this behavior isn't ideal, although I can see the case > > for viewing this as a mistake by the application developer: they are > > assuming that they know exactly when transactions begin, which is not > > a feature provided by their language interface. > > Well, actually, it's a bug in the interface IMHO. But as I said in the > last thread, it's a fairly widespread bug. I'm not sure that it is a client-side bug. For example Oracle seems to _always_ have a transaction going, i.e. you can't be "outside" of transaction, and you use just COMMIT to commit old _and_start_new_ transaction. IIRC the same is true for DB2. For these database the BEGIN TRANSACTION command is mainly used for starting nested transactions, which we don't have. > We've been taking the > position that the interface libraries should get fixed, and that's not > happening. It's probably time to look at a server-side fix. Maybe "fixing" the interface libraries would make them incompatible with *DBC's for all other databases in some subtle ways ? ----------------- Hannu