Re: query against pg_locks leads to large memory alloc

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: query against pg_locks leads to large memory alloc
From: Matheus de Oliveira <matioli.matheus@xxxxxxxxx>
Date: Mon, 18 Aug 2014 18:21:59 -0300
Cc: postgres performance list <pgsql-performance@xxxxxxxxxxxxxx>
In-reply-to: <CA+OQrzhdtpC-9enDpY_PTue3_eh9xxmP-z51fJHFqezvhJ-9Nw@mail.gmail.com>

On Mon, Aug 18, 2014 at 6:01 PM, Dave Owens <dave@xxxxxxxxxxxxx> 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

Follow-Ups:
- Re: query against pg_locks leads to large memory alloc
  - From: Merlin Moncure

References:
- query against pg_locks leads to large memory alloc
  - From: Dave Owens

Prev by Date: query against pg_locks leads to large memory alloc
Next by Date: Re: query against pg_locks leads to large memory alloc
Previous by thread: query against pg_locks leads to large memory alloc
Next by thread: Re: query against pg_locks leads to large memory alloc
Index(es):
- Date
- Thread

[Postgresql General] [Postgresql PHP] [PHP Users] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Yosemite]

Powered by Linux