Обсуждение: postgres generates too much processes per minute

Поиск
Список
Период
Сортировка

postgres generates too much processes per minute

От
"coliban@gmail.com"
Дата:
Hello,

i have the problem that postgres ist starting and stopping several (up
to 4)  processes per minute, so that the error log in windows is
running full, with more than 14 entries every minute.

Does someone know, how to reduce the start and the end of so many
processes, is there a variable or something ?

regards

Re: postgres generates too much processes per minute

От
Bill Moran
Дата:
In response to "coliban@gmail.com" <coliban@gmail.com>:

> Hello,
>
> i have the problem that postgres ist starting and stopping several (up
> to 4)  processes per minute, so that the error log in windows is
> running full, with more than 14 entries every minute.
>
> Does someone know, how to reduce the start and the end of so many
> processes, is there a variable or something ?

A process is started for every connection and ends when the connection
is closed.  If you're opening/closing connections frequently, you'll
see this.  It's by design.

Is the problem just that it's overwhelming the logs?  If so, you're
best bet is probably to reduce the amount of logging that occurs.

--
Bill Moran
Collaborative Fusion Inc.
http://people.collaborativefusion.com/~wmoran/

wmoran@collaborativefusion.com
Phone: 412-422-3463x4023

Re: postgres generates too much processes per minute

От
"Josh Tolley"
Дата:
On Thu, Jun 19, 2008 at 8:17 AM, Bill Moran
<wmoran@collaborativefusion.com> wrote:
> In response to "coliban@gmail.com" <coliban@gmail.com>:
>
>> Hello,
>>
>> i have the problem that postgres ist starting and stopping several (up
>> to 4)  processes per minute, so that the error log in windows is
>> running full, with more than 14 entries every minute.
>>
>> Does someone know, how to reduce the start and the end of so many
>> processes, is there a variable or something ?
>
> A process is started for every connection and ends when the connection
> is closed.  If you're opening/closing connections frequently, you'll
> see this.  It's by design.

You might consider using a connection pooler as well. The point of
such a thing is to allow applications requiring lots of connections to
share a smaller set of real connections to the database by proxying
connections. Look for pgBouncer and pgPool as example connection
pooling applications

- Josh / eggyknap