pg.ddx.io pgsql-sql@postgresql.org mailing list archivehelp / color / mirror / Atom feed
From: Keith Wong <keith@e-magine.com.au>
To: Colleen Williams <colleen@digital-arts.co.uk>
To: pgsql-sql@postgresql.org
Subject: Re: Persistent Connects (pg_pconnect)
Date: Wed, 22 Nov 2000 00:25:22 +1100
Message-ID: <4.3.2.7.0.20001122002515.00ad6238@mail.e-magine.com.au> (raw)
In-Reply-To: <4.3.2.7.2.20001121122024.00b41aa8@192.168.1.253>
Hi Colleen,
When you use specify a host parameter... Php will attempt to connect to
your postgres server using TCP/IP...
if you are not running the postgres backend with the -i option, then these
connections won't happen. When you don't
specify a host name then Php will use a local Unix socket.
Not sure about the persistant database connection stuff. What version of
Php are you using?
The only thing I could say, is to try explicitly closing the persistent
database connections in your Php code.
Maybe there is a bug in Php.
Hope this helps,
Keith.
At 12:34 PM 21/11/2000 +0000, Colleen Williams wrote:
>Hello all,
>
>I am having some problems with persistent connections.
>
>The PHP scripts in my content management system (CMS) are connecting using
>pg_pconnect(" dbname='MYDB' user='user' password='password''
>port='5432' "). I have not been able to connect to the PostgreSQL
>database when I include the host parameter in the pg_pconnect string and I
>don't understand why. Each time one of us uses the CMS, a new persistent
>connection process owned by postgres is started up. With 3 people
>accessing the CMS sporadically, 32 persistent connections are in existence
>and then Linux tells me there are too many connections! Sometimes I
>believe existing connections are reused but not often!
>
>Has anyone else had this sort of experience with persistent connections?
>It is driving me mad so I would appreciate any help or pointers you might have.
>
>Thanks,
>Colleen.
>
>Colleen Williams
>colleen@digital-arts.co.uk
>
>0207 484 8825
>
>Digital Arts | British Columbia House | 1 Regent Street | London | SW1Y 4NR
>http://www.digital-arts.co.uk
view thread (8+ messages) latest in thread
Message-ID: <4.3.2.7.0.20001122002515.00ad6238@mail.e-magine.com.au> Permalink: ../4.3.2.7.0.20001122002515.00ad6238@mail.e-magine.com.au/ Also on: postgresql.org/message-id/4.3.2.7.0.20001122002515.00ad6238@mail.e-magine.com.au ·
reply
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Reply to all the recipients from your mail client; the link fills in the headers below: reply via email Some clients, webmail especially, drop In-Reply-To and References from a link, and the reply then starts a new thread: use the mbox below. To: pgsql-sql@postgresql.org Cc: keith@e-magine.com.au, colleen@digital-arts.co.uk Subject: Re: Persistent Connects (pg_pconnect) In-Reply-To: <4.3.2.7.0.20001122002515.00ad6238@mail.e-magine.com.au> References: <4.3.2.7.2.20001121122024.00b41aa8@192.168.1.253> <4.3.2.7.0.20001122002515.00ad6238@mail.e-magine.com.au> * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox