Re: BUG #5756: postgres eat up all memory(2GB memory)

Поиск
Список
Период
Сортировка
От Craig Ringer
Тема Re: BUG #5756: postgres eat up all memory(2GB memory)
Дата
Msg-id 4CE4D7CF.3010200@postnewspapers.com.au
обсуждение исходный текст
Ответ на BUG #5756: postgres eat up all memory(2GB memory)  ("amos" <amosleaf@gmail.com>)
Список pgsql-bugs
"Amos"

This is not a bug. Your PostgreSQL install is misconfigured - you have
told it to use more memory than you have. Use a reasonable number of
max_connections, maybe as few as 20 or 30, and set c3p0 (your connection
pooler) to use one or two fewer than that. Your webapp's clients should
share the connections, and you should get MUCH, MUCH better results that
way, because your machine will spend less time thrashing and more time
getting real work done.

Feel free to ask for help on the postgresql-general mailing list if you
want further assistance.

http://www.postgresql.org/community/lists/

http://archives.postgresql.org/pgsql-general/

--
System & Network Administrator
POST Newspapers

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

Предыдущее
От: "amos"
Дата:
Сообщение: BUG #5756: postgres eat up all memory(2GB memory)
Следующее
От: Jon Nelson
Дата:
Сообщение: Re: Problem with ALTER TABLE - occasional "tuple concurrently updated"