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

Поиск
Список
Период
Сортировка
От Ahsan Ali
Тема Re: LOG: could not fork new process for connection: Cannot allocate memory
Дата
Msg-id CAGot2LWXVNuMVpA20fQH-hzbXDBQDeohHQbW=jxMwE2_zA+S+g@mail.gmail.com
обсуждение исходный текст
Ответ на Re: LOG: could not fork new process for connection: Cannot allocate memory  (John R Pierce <pierce@hogranch.com>)
Ответы Re: LOG: could not fork new process for connection: Cannot allocate memory
Список pgsql-general
Дерево обсуждения
yes it is older however we do apply security patches now a then. 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

Please let me know if you like to see any other logs and stuff

Regards
Ali

On Thu, Aug 25, 2016 at 4:51 PM, John R Pierce <pierce@hogranch.com> wrote:
On 8/25/2016 3:54 PM, Ahsan Ali wrote:
Red Hat Enterprise Linux Server release 6.3 (Santiago)

 that was released in June 2012, you're missing 4+ years of bug fixes, 6.8 is current.


max_connections = 3000

thats insanely high for most purposes unless you have several 100 CPU cores.

otherwise, hard to say whats failing, those log entries aren't giving much info.   How many connections are active (select count(*) from pg_stat_activity; ) when you get the error ?



-- 
john r pierce, recycling bits in santa cruz

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

Предыдущее
От: Tatsuki Kadomoto
Дата:
Сообщение: Re: incorrect checksum detected on "global/pg_filenode.map" when VACUUM FULL is executed
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Understanding Postgres Memory Usage