Postgres Pro
Downloads
Home   >   mailing lists

Re: query against pg_locks leads to large memory alloc - Mailing list pgsql-performance

From Merlin Moncure
Subject Re: query against pg_locks leads to large memory alloc
Date
Msg-id CAHyXU0w+haLQ2UdU_XjyiEPnC_Xp24QM4QjNYXFXQhtkvdSsgA@mail.gmail.com
Whole thread Raw
In response to Re: query against pg_locks leads to large memory alloc  (Matheus de Oliveira <matioli.matheus@gmail.com>)
Responses Re: query against pg_locks leads to large memory alloc
List pgsql-performance
Tree view 
On Mon, Aug 18, 2014 at 4:21 PM, Matheus de Oliveira
<matioli.matheus@gmail.com> wrote:
>
> On Mon, Aug 18, 2014 at 6:01 PM, Dave Owens <dave@teamunify.com> wrote:
>>
>> max_locks_per_transaction = 9000
>> max_pred_locks_per_transaction = 40000

performance of any query to pg_locks is proportional to the setting of
max_locks_per_transaction.  still, something is awry here.  can you
'explain' that query?  also, what's the answer you get when:

SELECT COUNT(*) from pg_locks;

?
merlin

pgsql-performance by date:

Previous
From: Matheus de Oliveira
Date:
Subject: Re: query against pg_locks leads to large memory alloc
Next
From: Dave Owens
Date:
Subject: Re: query against pg_locks leads to large memory alloc