Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id AA6CF475F09 for ; Mon, 18 Nov 2002 12:13:00 -0500 (EST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id D63D6475F26 for ; Mon, 18 Nov 2002 12:12:59 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.5/8.12.5) with ESMTP id gAIHChhR000251; Mon, 18 Nov 2002 12:12:44 -0500 (EST) To: David Wheeler Cc: Tim Bunce , dbi-dev@perl.org, pgsql-interfaces@postgresql.org Subject: Re: DBD::PostgreSQL In-reply-to: <85B2FBF1-FB16-11D6-93B3-0003931A964A@wheeler.net> References: <85B2FBF1-FB16-11D6-93B3-0003931A964A@wheeler.net> Comments: In-reply-to David Wheeler message dated "Mon, 18 Nov 2002 08:55:20 -0800" Date: Mon, 18 Nov 2002 12:12:43 -0500 Message-ID: <250.1037639563@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200211/59 X-Sequence-Number: 3307 David Wheeler writes: > I'm quite sure that in PostgreSQL, transactions have to be started > explicitly. As of 7.3 that's not necessarily so anymore; you can "SET autocommit TO off" and get the behavior where any statement starts a transaction block (and so an explicit COMMIT is required to commit its effects). Not sure if this helps you or not. regards, tom lane