Bug #14070 Updated: Segfault with concurrent postgres connections
| From: | sniper@php.net | Date: | Fri, 16 Nov 2001 00:17:31 +0000 |
| Subject: | Bug #14070 Updated: Segfault with concurrent postgres connections | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-70610@lists.php.net to get a copy of this message | ||
ID: 14070
Updated by: sniper
Reported By: mw@sime.com
Old Status: Open
Status: Closed
Old Bug Type: Reproducible crash
Bug Type: PostgreSQL related
Operating System: Linux 2.2.19ext3
PHP Version: 4.0.6
New Comment:
This should be fixed in CVS. Try latest CVS snapshot from
http://snaps.php.net/ and if it doesn't work, reopen this
bug report.
Previous Comments:
------------------------------------------------------------------------
[2001-11-15 11:09:25] mw@sime.com
PHP segfaults in several places, when the following conditions occur:
1. two or more concurrent connections from the same script to the same datebase, with EXACTLY the
same connect string.
2. one of the links must be closed
3. the other link is used
4. postgres sends notices (e.g. rollback; commit) etc.
the problem is in pgsql.c/php_pgsql_do_connect(), around line 443. it uses the connect string as
hash key to find such a connection, and if subsequenct connect calls use the same connect string,
the connection seems to be reused (which is wrong. it should NOT be reused).
the effects vary, sometimes it segfaults, sometimes not.
------------------------------------------------------------------------
Edit this bug report at http://bugs.php.net/?id=14070&edit=1