Skip site navigation (1) Skip section navigation (2)

Re: php and connection

From: Szymon Guz <mabewlun(at)gmail(dot)com>
To: Thom Brown <thombrown(at)gmail(dot)com>
Cc: jd(at)commandprompt(dot)com, PostgreSQL List <pgsql-general(at)postgresql(dot)org>
Subject: Re: php and connection
Date: 2010-06-30 18:56:09
Message-ID: AANLkTilHvM4qbAjFLLY54SJ-j_mTQ3rjHax-fLTeq9Ul@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-general
2010/6/30 Thom Brown <thombrown(at)gmail(dot)com>

> On 30 June 2010 19:43, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
> > On Wed, 2010-06-30 at 20:42 +0200, Szymon Guz wrote:
> >> Hi,
> >> in a PHP application working on Postgres normally the new connection
> >> to the database is made per request.
> >>
> >>
> >> This can potentially cause too big overhead, so I've got some
> >> questions:
> >>
> >>
> >> - is the overhead really noticeable?
> >
> > It can be.
> >
> >> - could this be solved using persistent connections, or the persistent
> >> connections in php and postgres don't work properly?
> >
> > Don't use them.
> >
> >> - could this be solved using something like pgpool?
> >>
> > Yes, using a connection pooler will solve the problem. I prefer
> > pgbouncer.
> >
>
> +1
>
> I can't really add to that.
>
> Thom
>

Thanks for the answers that ensured me in what I was thinking about.

regards
Szymon

In response to

pgsql-general by date

Next:From: ZoidDate: 2010-06-30 19:08:38
Subject: LINE 1: IDENTIFY_SYSTEM error infinitum
Previous:From: MDDate: 2010-06-30 18:53:10
Subject: Re: Looking for multithreaded build of libpq for Windows

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group