From: | Renato Oliveira <Renato(dot)Oliveira(at)cantabcapital(dot)com> |
---|---|
To: | Forums postgresql <pgsql-general(at)postgresql(dot)org>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | How Many PG_Locks are considered too many |
Date: | 2015-07-30 10:13:22 |
Message-ID: | 387405ED5B94BF42B91A9AB5BB14498E53A61241@ccpexch05.cantab.local |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-general |
Hi
I have few questions, if anyone could help me, it will be very much appreciated.
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?
Thank you
Renato
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2015-07-30 13:49:28 | Re: How Many PG_Locks are considered too many |
Previous Message | Harshad Adalkonda | 2015-07-29 05:56:20 | Re: more is not recognized as an internal or external command, operable program or batch file in psql in windows 7 |
From | Date | Subject | |
---|---|---|---|
Next Message | Rowan Collins | 2015-07-30 12:35:18 | Exclusively locking parent tables while disinheriting children. |
Previous Message | Alban Hertroys | 2015-07-30 09:57:29 | Re: Question about copy from with timestamp format |