Re: [ADMIN] How Many PG_Locks are considered too many - Mailing list pgsql-general

From Renato Oliveira
Subject Re: [ADMIN] How Many PG_Locks are considered too many
Date
Msg-id 101FA6D2-BBB6-4A9E-B977-CF0EA4B35757@cantabcapital.com
Whole thread Raw
In response to Re: [ADMIN] How Many PG_Locks are considered too many  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: [ADMIN] How Many PG_Locks are considered too many  (John Scalia <jayknowsunix@gmail.com>)
List pgsql-general
Peter thank you much appreciated

Sent from my iPhone

> On 30 Jul 2015, at 14:54, Peter Eisentraut <peter_e@gmx.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.
>



pgsql-general by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [ADMIN] How Many PG_Locks are considered too many
Next
From: Adrian Klaver
Date:
Subject: Re: user connection not recorded?