Re: [phplib] mysql_pconnect at db_mysql.inc From: Davor Cengija (davor <email protected>)
Date: 08/10/00

On Wed, 9 Aug 2000, Jota Matsubara wrote:

>Hello.
>
>I'm using MySQL + PHP3 + PHPlib-7.2b, and lately having
>the problem of having too much MySQL process running
>on server after running for few days.
>I noticed in db_mysql.inc, mysql_pconnect was used and
>thought this may be part of the problem. As far as I
>saw, I found no reason to use mysql_pconnect instead of
>mysql_connect, which is safer.
>
>Would it cause any trouble if I just change mysql_pconnect
>to mysql_connect ?

        If you check the mailing list archive, you'll find a thread
        about the similar issues. If I remember correctly, the person
        which had the similar problems you have now just changed
        _pconnect to _connect and every seemed to be fine.

        _pconnect is used when you want to accomplish a kind of
        'connection pooling' and _connect just connects to the
        database for every db call, so it should be a little bit
        slower. 

-- 
      v
Davor Cengija
davor <email protected>
============================
"Nicht in die Augen bringen"

---------------------------------------------------------------------
To unsubscribe, e-mail: phplib-unsubscribe <email protected>
For additional commands, e-mail: phplib-help <email protected>