Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 7C8D29FB9FE for ; Mon, 5 Mar 2007 05:30:08 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-new, port 10024) with ESMTP id 40390-01 for ; Mon, 5 Mar 2007 05:30:01 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.244]) by postgresql.org (Postfix) with ESMTP id 4D3B89FB9C7 for ; Mon, 5 Mar 2007 05:30:04 -0400 (AST) Received: by an-out-0708.google.com with SMTP id c24so1279663ana for ; Mon, 05 Mar 2007 01:30:03 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=r9+vAna2eiJcBCItF/L5ieDp6jTzgx4juuIgAkT+ucKNr3tAC/G9l0fZ3X8uaA/3PSYJv/fNhEHdY+d5+SpTG+w9yB+mqSNEZ/75ok27Ng1aIIAHC3SyPqeYWXVw5cpuf4yssh2f3lLWcZcbDx2FoY+nZycAeJASon1p4GAwZ5w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=RguTtkX1P2HBHTxYzAU6gywdIrIounLoetT5NiUZCk3n53BAvcL1CwfyXTiHYwk+6xCPPydmLvI3wXJCndLIkVbOXodxCmQLqnLwGN0rin96vDbr/ikuyQJ+4t6y/hJi2yFxNIhRklhCSqq+voeo0kZUNyjd7i/j2JGhRz6O16k= Received: by 10.100.11.7 with SMTP id 7mr4035576ank.1173087003202; Mon, 05 Mar 2007 01:30:03 -0800 (PST) Received: by 10.100.165.1 with HTTP; Mon, 5 Mar 2007 01:30:03 -0800 (PST) Message-ID: Date: Mon, 5 Mar 2007 10:30:03 +0100 From: mikie To: pgsql-php@postgresql.org Subject: Re: transactions from PHP - double COMMIT required? In-Reply-To: <45E81DC5.6090308@bugs.unl.edu.ar> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <45E70C9A.200@bugs.unl.edu.ar> <200703011353.07621.xzilla@users.sourceforge.net> <45E81DC5.6090308@bugs.unl.edu.ar> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200703/20 X-Sequence-Number: 3732 2007/3/2, Martin Marques : > mikie wrote: > > 2007/3/1, Robert Treat : > >> Yeah, do the above recommendation to see if all of your statements are > >> making > >> thier way into pg > > > > OK, I have checked the logs. I can see both COMMIT statements in the > > log - the first commit from my transaction and then the other that I > > send to workaround the problem. > > There must be some other problem. Do you have trasaction ID on the logs? > See if both commits go in the same transaction. Could you please advise me how to check the transaction ID in the log? > Any errors during the transaction? As I wrote in my first post, I make this error intentionally to check if transaction works (if something fails, then the entire transaction should be rolled back). I intentionally give wrong data in the "date" field for example. Perhaps I should ask again: is it my responsibility to check if the transaction failed and issue a ROLLBACK command, or will the PG server do it automatically?