Re: How Many PG_Locks are considered too many

From: Renato Oliveira <Renato(dot)Oliveira(at)cantabcapital(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Forums postgresql <pgsql-general(at)postgresql(dot)org>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: How Many PG_Locks are considered too many
Date: 2015-07-30 13:57:07
Message-ID: 101FA6D2-BBB6-4A9E-B977-CF0EA4B35757@cantabcapital.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-general

Peter thank you much appreciated

Sent from my iPhone

> On 30 Jul 2015, at 14:54, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
>
>> On 7/30/15 6:13 AM, Renato Oliveira wrote:
>> We have a Nagios plugin, which monitors pg_locks and almost daily we see
>> 3000 to 40000 pg_locks.
>>
>> Can we just ignore them, can we let them grow without worrying?
>>
>> How many pg_locks are considered unsafe for any given postgres server?
>
> That depends on how many concurrent clients you have and what they are
> doing. Every table access will at least create a share lock of some
> kind, so if you have a lot of activity that does a lot of things, you
> will see a lot of locks, but that doesn't impact database performance in
> a significant way.
>
> I don't think monitoring the absolute number of locks is useful. You
> might want to chart it, to compare over time. If you want to monitor
> locks, you could monitor lock waits, which you can get by checking the
> server log.
>

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message John Scalia 2015-07-30 14:19:59 Re: [ADMIN] How Many PG_Locks are considered too many
Previous Message Peter Eisentraut 2015-07-30 13:49:28 Re: How Many PG_Locks are considered too many

Browse pgsql-general by date

  From Date Subject
Next Message Ramesh T 2015-07-30 14:08:39 Re: instr detail
Previous Message Peter Eisentraut 2015-07-30 13:49:28 Re: How Many PG_Locks are considered too many