Re: Process in state BIND, authentication, PARSE - Mailing list pgsql-performance

From Michael Paquier
Subject Re: Process in state BIND, authentication, PARSE
Date
Msg-id CAB7nPqRNndfTHnUz4W16YuYvZ_Ux7xVtm9H6Z4wHKKCtqRkZ9A@mail.gmail.com
Whole thread Raw
In response to Re: Process in state BIND, authentication, PARSE  (Jeison Bedoya <jeisonb@audifarma.com.co>)
Responses Re: Process in state BIND, authentication, PARSE  (Merlin Moncure <mmoncure@gmail.com>)
List pgsql-performance
On Tue, Jul 9, 2013 at 2:01 AM, Jeison Bedoya <jeisonb@audifarma.com.co> wrote:
> max_connections = 900
> work_mem = 1024MB
> maintenance_work_mem = 1024MB
Aren't work_mem and maintenance_work_mem too high? You need to keep in
mind that those are per-operation settings, so for example if you have
100 clients performing queries, this could grow up to 100G. In your
case you even have a maximum of 900 connections... Do you perform
heavy sort operations with your application that could explain such an
amount of memory needed?
--
Michael


pgsql-performance by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Performance autovaccum
Next
From: Merlin Moncure
Date:
Subject: Re: Process in state BIND, authentication, PARSE