Re: [pgadmin-support] Database has been killed after increasing memory

Hi,

+Adding postgresql general list. Hope, some one will provide more
information.

On Mon, Dec 23, 2013 at 1:56 PM, kolszew73(at)gmail(dot)com <kolszew73(at)gmail(dot)com>wrote:

> 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?
>

Using EXPLAIN ANALYZE BUFFERS

> How can I protect my postgres server, when i don't know exactly how
> complicated queries creates my customer, e.g. in reports?
>

Using pgbadger/pgfounie tools, you will get the detailed statistical report.

Regards,
Dinesh

>
>
>
>
>
> --
> 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.
>
>
> --
> Sent via pgadmin-support mailing list (pgadmin-support(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgadmin-support
>