Обсуждение: Monitoring Locks in Databases

We are using Postgres 7.1.2 on a Sun E3500 running Solaris 6.

Is their some way to monitor database locks in Postgres (ie. how many and
who owns the locks")? If not, do we foresee this happening in some later
release?

This would be very useful for us in debugging.

Naomi

Hi,

I think it will be possible in PGSQL 7.3 there exists somthing
like pg_locks

regds
mallah.

> We are using Postgres 7.1.2 on a Sun E3500 running Solaris 6.
>
> Is their some way to monitor database locks in Postgres (ie. how many and who owns the locks")?
> If not, do we foresee this happening in some later release?
>
> This would be very useful for us in debugging.
>
> Naomi
>
>
> ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and
> unsubscribe commands go to majordomo@postgresql.org



-----------------------------------------
Get your free web based email at trade-india.com.
   "India's Leading B2B eMarketplace.!"
http://www.trade-india.com/

Pgmonitor is pretty good for this.  It doesn't give you the ability to
traverse from session to lock to resource to lock to session that would be
nice to trace through multiple user interwoven lock contention problems.
But is does provide an invaluable window into who's doing what right now
against the database to see if session are waiting for locks or not.

Marc Mitchell - Senior Application Architect
Enterprise Information Solutions, Inc.
Downers Grove, IL 60515
marcm@eisolution.com

----- Original Message -----
From: "Naomi Walker" <nwalker@eldocomp.com>
To: <pgsql-admin@postgresql.org>
Sent: Friday, September 13, 2002 1:41 PM
Subject: [ADMIN] Monitoring Locks in Databases


> We are using Postgres 7.1.2 on a Sun E3500 running Solaris 6.
>
> Is their some way to monitor database locks in Postgres (ie. how many and
> who owns the locks")? If not, do we foresee this happening in some later
> release?
>
> This would be very useful for us in debugging.
>
> Naomi
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org