| From: | Thom Brown <thombrown(at)gmail(dot)com> |
|---|---|
| To: | jd(at)commandprompt(dot)com |
| Cc: | Szymon Guz <mabewlun(at)gmail(dot)com>, PostgreSQL List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: php and connection |
| Date: | 2010-06-30 18:45:56 |
| Message-ID: | AANLkTilyeUDL81P9_7OmKQaGZLrwQKWPDOtKuek3qWei@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | MD | 2010-06-30 18:53:10 | Re: Looking for multithreaded build of libpq for Windows |
| Previous Message | Joshua D. Drake | 2010-06-30 18:43:25 | Re: php and connection |