Re: query against pg_locks leads to large memory alloc

From: Matheus de Oliveira <matioli(dot)matheus(at)gmail(dot)com>
To: Dave Owens <dave(at)teamunify(dot)com>
Cc: postgres performance list <pgsql-performance(at)postgresql(dot)org>
Subject: Re: query against pg_locks leads to large memory alloc
Date: 2014-08-18 21:21:59
Message-ID: CAJghg4+y5NcvjfJO+Ynad-5NcuHHOUOgFpUEP=fLA3WTgGAoCw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Mon, Aug 18, 2014 at 6:01 PM, Dave Owens <dave(at)teamunify(dot)com> wrote:

> max_locks_per_transaction = 9000
> max_pred_locks_per_transaction = 40000
>

Do you really need such large values? What is your max_connections value?

Regards,
--
Matheus de Oliveira
Analista de Banco de Dados
Dextra Sistemas - MPS.Br nível F!
www.dextra.com.br/postgres

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Merlin Moncure 2014-08-18 21:29:10 Re: query against pg_locks leads to large memory alloc
Previous Message Dave Owens 2014-08-18 21:01:30 query against pg_locks leads to large memory alloc