Database has been killed after increasing memory - Mailing list pgadmin-support

From kolszew73@gmail.com
Subject Database has been killed after increasing memory
Date
Msg-id 1387787209159-5784404.post@n5.nabble.com
Whole thread Raw
List 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 by date:

Previous
From: Guillaume Lelarge
Date:
Subject: Re: pgadmin3-1.18.1//pgadmin/dd/ddmodel/ddDBReverseEnginering.cpp: 2 * bad if test ?
Next
From: Karl-Philipp Richter
Date:
Subject: [bug report] underscores in table cell not visible