Re: Too many clients to Postgresql server
От | Robert Treat |
---|---|
Тема | Re: Too many clients to Postgresql server |
Дата | |
Msg-id | 1027003702.22899.36.camel@camel обсуждение исходный текст |
Ответ на | Too many clients to Postgresql server (Siva Kumar <siva@leatherlink.net>) |
Ответы |
Re: Too many clients to Postgresql server
|
Список | pgsql-general |
Since you don't have the ability to bump up the maximum number of connections, your best bet is to switch to pg_connect. The implications would be that each page load will require a connection to the server, but unless you are doing multiple database *connections* per page, this impact is usually insignificant. Robert Treat On Thu, 2002-07-18 at 15:09, Siva Kumar wrote: > This message uses a character set that is not supported by the Internet > Service. To view the original message content, open the attached > message. If the text doesn't display correctly, save the attachment to > disk, and then open it using a viewer that can display the original > character set. <<message.txt>> > ---- > > We have a website using postgresql and php, hosted in a shared server. The > settings for the maximum connections allowed is 32. > > I have used the persistent connection function pg_pconnect for all the > database connections. For the past one week I have started getting the > maximum number of clients reached message now and then. Today one of my > customers also called up with the same problem. > > The question is, should I change the way of connecting to the server to > pg_connect? What will be the implications? Otherwise, how can the persistent > connections be closed down? > > Thanks and best regards, > > > Siva Kumar
В списке pgsql-general по дате отправления: