Re: Monitoring Locks in Databases - Mailing list pgsql-admin
| From | Marc Mitchell |
|---|---|
| Subject | Re: Monitoring Locks in Databases |
| Date | |
| Msg-id | [email protected] Whole thread Raw |
| In response to | Monitoring Locks in Databases (Naomi Walker <[email protected]>) |
| List | pgsql-admin |
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 [email protected] ----- Original Message ----- From: "Naomi Walker" <[email protected]> To: <[email protected]> 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 [email protected]
pgsql-admin by date: