Re: Process in state BIND, authentication, PARSE

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Jeison Bedoya <jeisonb(at)audifarma(dot)com(dot)co>
Cc: PostgreSQL mailing lists <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Process in state BIND, authentication, PARSE
Date: 2013-07-08 22:35:14
Message-ID: CAB7nPqRNndfTHnUz4W16YuYvZ_Ux7xVtm9H6Z4wHKKCtqRkZ9A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Tue, Jul 9, 2013 at 2:01 AM, Jeison Bedoya <jeisonb(at)audifarma(dot)com(dot)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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Merlin Moncure 2013-07-09 13:23:39 Re: Process in state BIND, authentication, PARSE
Previous Message Michael Paquier 2013-07-08 22:21:30 Re: Performance autovaccum