ID: 14196 User updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Old Status: Feedback Status: Open Bug Type: PostgreSQL related Operating System: Redhat 6.2 PHP Version: 4.0.6 New Comment:
To be clear, this is not a perfectly legal use of commit or rollback because a begin work statement should precede them. If begin work is used everything is fine. Previous Comments: ------------------------------------------------------------------------ [2001-11-23 08:26:29] [EMAIL PROTECTED] an you try with latest RC and see if it works http://www.php.net/~zeev/php-4.1.0RC3.tar.gz Feedback. ------------------------------------------------------------------------ [2001-11-23 08:13:45] [EMAIL PROTECTED] Write something which makes an explicit commit before disconnecting from postgres, but do not make any transactions. A notice is going to appear in the postgresql log saying that a commit without transactions is made and the same notice is going to appear in the apache error log as well. The problem is that 5 times out of 10 Apache is also going to segfault. We had this kind of "commit if no sql_error was recognized" in our system and noticed the segfaults in the apache log. We removed the commit and all the segfaults are gone from then on. Postgresql 7.1.3. and PHP4.0.6. './configure' '--with-oci8' '--with-apache=/coca/install/apache_1.3.22/' '--enable-sigchild' '--enable-track-vars' '--with-mysql' '--with-pgsql=/usr/local/pgsql' ------------------------------------------------------------------------ Edit this bug report at http://bugs.php.net/?id=14196&edit=1 -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
