Bug->Doc #64549 [Opn->Ver]: mysqlnd persistent connection handling are not properly pooling

From: Date: Mon, 21 Jun 2021 09:34:38 +0000
Subject: Bug->Doc #64549 [Opn->Ver]: mysqlnd persistent connection handling are not properly pooling
References: 1  Groups: php.doc.bugs 
Request: Send a blank email to doc-bugs+get-18890@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=64549&edit=1

 ID:                 64549
 Updated by:         cmb@php.net
 Reported by:        rgagnon24 at gmail dot com
 Summary:            mysqlnd persistent connection handling are not
                     properly pooling
-Status:             Open
+Status:             Verified
-Type:               Bug
+Type:               Documentation Problem
 Package:            PDO MySQL
 Operating System:   CentOS 5.9
 PHP Version:        5.3.23
-Assigned To:        cmb
+Assigned To:        
 Block user comment: N
 Private report:     N

 New Comment:

Indeed, the persistent connections and the stats are stored
separately for each worker process (or thread), so in a typical
scenario with multiple workers, pooling may not work as expected.
The respective documentation[1] should clarify that; the note
about ODBC connection pooling already hints at this, but is not
general enough.

[1] <https://www.php.net/manual/en/pdo.connections.php>


Previous Comments:
------------------------------------------------------------------------
[2021-06-20 08:30:25] wf3f2g dot wf2f3f at egrg dot dd

maybe you don't understand that each worker process has it's own persistent connection and
that every client connection to the Webserver may be handled by a different worker

so in the reality you have sooner or later the number of max worker processes mysql connections and
hence the concept of persistent database connections is idiotic

------------------------------------------------------------------------
[2021-06-20 06:07:36] rgagnon24 at gmail dot com

Changing Summary

------------------------------------------------------------------------
[2021-06-20 06:06:34] rgagnon24 at gmail dot com

Why is it I received an email that said I could re-open the case if the problem still exists, yet
when I do (which the correct password), it says "you are not allowed to change a ticket to that
state" (or something like that

------------------------------------------------------------------------
[2021-06-20 06:05:46] rgagnon24 at gmail dot com

Why is it I received an email that said I could re-open the case if the problem still exists, yet
when I do (which the correct password), it says "

------------------------------------------------------------------------
[2021-06-20 06:04:29] rgagnon24 at gmail dot com

The bug as originally posted by me over 8 years ago still exists.  I don't understand the
question "which bug?" asked by cmb@php.net.

As originally posted, the bug exists, the test script exploits it, and the expected results vs.
actual results are shown.

------------------------------------------------------------------------


The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

    https://bugs.php.net/bug.php?id=64549


--
Edit this bug report at https://bugs.php.net/bug.php?id=64549&edit=1


Thread (3 messages)

« previous php.doc.bugs (#18890) next »