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 d850ad5e-a2b1-f313-b187-742f500a73a8@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 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 по дате отправления:

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