Re: LOG: could not fork new process for connection: Cannot allocate memory

Поиск
Список
Период
Сортировка
От John R Pierce
Тема Re: LOG: could not fork new process for connection: Cannot allocate memory
Дата
Msg-id 1c7aeb24-2611-b2a9-2dad-8cde06fe60ad@hogranch.com
обсуждение исходный текст
Ответ на Re: LOG: could not fork new process for connection: Cannot allocate memory  (Ahsan Ali <ali95695@gmail.com>)
Ответы Re: LOG: could not fork new process for connection: Cannot allocate memory  (Ahsan Ali <ali95695@gmail.com>)
Список pgsql-general
On 8/25/2016 5:10 PM, Ahsan Ali wrote:
> yes it is older however we do apply security patches now a then.

redhat doesn't really support mixing packages from different releases,
they only test things with all packages from the same snapshot.   "yum
update" should bring the whole system up to current.


> regarding max connection its the application design however it does
> not have that many active session.
> postgres=# select count(*) from pg_stat_activity;
>  count
> -------
>   1818

so there were 1818 postgres client processes at the time it coudln't
create a new process.   thats certainly a larger number than I've ever
run.   if I have client software that has lots and lots of idle
connections, I use a connection pooler like pgbouncer, in transaction mode.

--
john r pierce, recycling bits in santa cruz



В списке pgsql-general по дате отправления:

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: incorrect checksum detected on "global/pg_filenode.map" when VACUUM FULL is executed
Следующее
От: Ahsan Ali
Дата:
Сообщение: Re: LOG: could not fork new process for connection: Cannot allocate memory