Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 37633633324 for ; Fri, 1 May 2009 18:03:13 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 57148-04 for ; Fri, 1 May 2009 18:03:06 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail.potentialtech.com (internet.potentialtech.com [66.167.251.6]) by mail.postgresql.org (Postfix) with ESMTP id 135B6632DA5 for ; Fri, 1 May 2009 18:03:05 -0300 (ADT) Received: from vanquish.ws.pitbpa0.priv.collaborativefusion.com (pr40.pitbpa0.pub.collaborativefusion.com [206.210.89.202]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.potentialtech.com (Postfix) with ESMTPSA id A08CAEBC0A for ; Fri, 1 May 2009 17:03:03 -0400 (EDT) Date: Fri, 1 May 2009 17:03:02 -0400 From: Bill Moran To: pgsql-php@postgresql.org Subject: pg_transaction_status() unreliable?! Message-Id: <20090501170302.2eb5eb84.wmoran@potentialtech.com> X-Mailer: Sylpheed 2.6.0 (GTK+ 2.14.7; i386-portbld-freebsd7.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.333 tagged_above=0 required=5 tests=PLING_QUERY=1.333 X-Spam-Level: * X-Archive-Number: 200905/1 X-Sequence-Number: 4021 I'm having some ugly fun here. It doesn't seem as if pg_transaction_status() is reliable in the least. For example, I'm doing the equivalent of the following: pg_send_query_params($conn, 'BEGIN', array()); pg_get_result($conn); ... some other queries, each using pg_send_query_params() and pg_get_result() ... pg_send_query_params($conn, 'COMMIT', array()); pg_get_result($conn); echo pg_transaction_status($conn); Now, amazingly enough, pg_transaction_status() returns PGSQL_TRANSACTION_ACTIVE after the commit. This makes no sense to me at all ... it should return PGSQL_TRANSACTION_IDLE, since the connection is no longer in a transaction. Is anyone else seeing this? I have assertions failing all over the place because my code thinks that transactions have been left uncommitted. Postgresql 8.3.5, FreeBSD 6.3, PHP 5.2.9 with Suhosin patch -- Bill Moran http://www.potentialtech.com http://people.collaborativefusion.com/~wmoran/