| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Szymon Guz <mabewlun(at)gmail(dot)com> |
| Cc: | PostgreSQL List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: php and connection |
| Date: | 2010-06-30 18:43:25 |
| Message-ID: | 1277923405.20538.2771.camel@jd-desktop.unknown.charter.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
Joshua D. Drake
>
> regards
> Szymon
--
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.commandprompt.com/ - 509.416.6579
Consulting, Training, Support, Custom Development, Engineering
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thom Brown | 2010-06-30 18:45:56 | Re: php and connection |
| Previous Message | Szymon Guz | 2010-06-30 18:42:17 | php and connection |