php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Doc Bug #25552 Documentation unclear about persistent database connections
Submitted: 2003-09-15 17:44 UTC Modified: 2004-04-08 01:41 UTC
Votes:1
Avg. Score:3.0 ± 0.0
Reproduced:0 of 0 (0.0%)
From: grange at club-internet dot fr Assigned:
Status: Not a bug Package: Documentation problem
PHP Version: Irrelevant OS:
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
(description)
Block user comment
Status: Assign to:
Package:
Bug Type:
Summary:
From: grange at club-internet dot fr
New email:
PHP Version: OS:

 

 [2003-09-15 17:44 UTC] grange at club-internet dot fr
Description:
------------
Hello,

The documentation about persistent db connections (ie. chapter 21 of the manual) should probably be more clear whether connections are persistent across *subsequent http requests served by different apache child processes* or persistent across *subsequent http requests served by the same child process* (or is it none if the above... oh well 8-)). 

The french translation clearly states the first, while as I'm reading the english documentation (and the first user contributed note), I understand the oci8 extension (as well as other extensions providing persistent connections) behaves the second way.

Theorically, in the second case, the number of db connections should increase to MaxClients, where in the first case, (ignoring peak activity) it should be less, depending on the percentage of db-driven pages out of static pages (ie for 5% of db pages, 5% of MaxClients).

Anyway, thanks for the great work !


Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2004-04-08 01:41 UTC] irchtml@php.net
Quote from the manual:

They cause the child process to simply connect only once for its entire lifespan, instead of every time it processes a page that requires connecting to the SQL server. This means that for every child that opened a persistent connection will have its own open persistent connection to the server. For example, if you had 20 different child processes that ran a script that made a persistent connection to your SQL server, you'd have 20 different connections to the SQL server, one from each child.
---
Each child would have it's own connection, so the latter case in your report would be true.  Hope that clears it up.  If you have any further suggestions please feel free to e-mail phpdoc@lists.php.net.  Thank you!
 
PHP Copyright © 2001-2021 The PHP Group
All rights reserved.
Last updated: Fri Sep 24 07:03:37 2021 UTC