Re: Monitoring Locks in Databases
От | Marc Mitchell |
---|---|
Тема | Re: Monitoring Locks in Databases |
Дата | |
Msg-id | 005701c25b69$35d2db20$7b01050a@eisolution.com обсуждение исходный текст |
Ответ на | Monitoring Locks in Databases (Naomi Walker <nwalker@eldocomp.com>) |
Список | 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 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
В списке pgsql-admin по дате отправления: