Re: query against pg_locks leads to large memory alloc

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: Dave Owens <dave(at)teamunify(dot)com>
Cc: Merlin Moncure <mmoncure(at)gmail(dot)com>, Matheus de Oliveira <matioli(dot)matheus(at)gmail(dot)com>, postgres performance list <pgsql-performance(at)postgresql(dot)org>
Subject: Re: query against pg_locks leads to large memory alloc
Date: 2014-08-19 17:17:10
Message-ID: 20140819171710.GA15735@awork2.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On 2014-08-18 14:36:52 -0700, Dave Owens wrote:
> On Mon, Aug 18, 2014 at 2:21 PM, Matheus de Oliveira
> <matioli(dot)matheus(at)gmail(dot)com> wrote:
> > Do you really need such large values? What is your max_connections value?
>
> max_connections = 450 ...we have found that we run out of shared
> memory when max_pred_locks_per_transaction is less than 30k.

What was the precise error message when that happened?

Greetings,

Andres Freund

--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Dave Owens 2014-08-19 17:25:50 Re: query against pg_locks leads to large memory alloc
Previous Message Dave Owens 2014-08-19 17:14:45 Re: query against pg_locks leads to large memory alloc