Database has been killed after increasing memory

Поиск
Список
Период
Сортировка
От kolszew73@gmail.com
Тема Database has been killed after increasing memory
Дата
Msg-id 1387787209159-5784404.post@n5.nabble.com
обсуждение исходный текст
Список pgadmin-support
Hi

I Have problem with "postmaster" processes which unexpectedly consume very
big amount of memory, about 200MB!!!, and as a consequence whole available
memory in Linux, and as a consequence Linux kills postmasters processes :(

my configuration:
8 Core
8 GB RAM
max_connections = 60
work_mem = 32MB
shared_buffers = 2G

After an investigation, I suspect, than some of my queries which contains
many INNER JOIN's (about 30, and one of them about 60) probably causes
memory problem.

What are postgres limitations about JOINS in one query?
How can I estimate memory needed for postgres?
How can I protect my postgres server, when i don't know exactly how
complicated  queries creates my customer, e.g. in reports? 





--
View this message in context:
http://postgresql.1045698.n5.nabble.com/Database-has-been-killed-after-increasing-memory-tp5784404.html
Sent from the PostgreSQL - pgadmin support mailing list archive at Nabble.com.



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

Предыдущее
От: Guillaume Lelarge
Дата:
Сообщение: Re: pgadmin3-1.18.1//pgadmin/dd/ddmodel/ddDBReverseEnginering.cpp: 2 * bad if test ?
Следующее
От: Karl-Philipp Richter
Дата:
Сообщение: [bug report] underscores in table cell not visible