Database has been killed after increasing memory

From: "kolszew73(at)gmail(dot)com" <kolszew73(at)gmail(dot)com>
To: pgadmin-support(at)postgresql(dot)org
Subject: Database has been killed after increasing memory
Date: 2013-12-23 08:26:49
Message-ID: 1387787209159-5784404.post@n5.nabble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support pgsql-general

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.

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message Dinesh Kumar 2013-12-23 09:14:35 Re: [pgadmin-support] Database has been killed after increasing memory
Previous Message Guillaume Lelarge 2013-12-21 16:59:08 Re: pgadmin3-1.18.1//pgadmin/dd/ddmodel/ddDBReverseEnginering.cpp: 2 * bad if test ?

Browse pgsql-general by date

  From Date Subject
Next Message Dinesh Kumar 2013-12-23 09:14:35 Re: [pgadmin-support] Database has been killed after increasing memory
Previous Message Anand Kumar, Karthik 2013-12-23 02:59:21 Re: index and table corruption