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

From Kevin Grittner
Subject Re: Process in state BIND, authentication, PARSE
Date
Msg-id 1373463453.36614.YahooMailNeo@web162904.mail.bf1.yahoo.com
Whole thread Raw
In response to Re: Process in state BIND, authentication, PARSE  (Jeison Bedoya <jeisonb@audifarma.com.co>)
List pgsql-performance
Jeison Bedoya <jeisonb@audifarma.com.co> wrote:

> Ram: 128GB

> max_connections = 900

> temp_buffers = 128MB

Besides the concerns already expressed about work_mem, temp_buffers
could be a big problem.  If a connection uses temp tables it
acquires up to 128MB, *and holds on it reserved for caching temp
tables for that connection for as long as the connection lasts*.
So, for 900 connections, that could be 112.5 GB.  I would expect to
see performance decrease and eventually completely tank as more
connections reserved memory for this purpose.

--
Kevin Grittner
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-performance by date:

Previous
From: Rick Otten
Date:
Subject: Re: Performance autovaccum
Next
From: "Huang, Suya"
Date:
Subject: how to speed up the index creation in GP?