| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Dale Anderson <danderso(at)crystalsugar(dot)com>, pgsql-general(at)postgreSQL(dot)org |
| Subject: | Re: Table locks |
| Date: | 2000-10-09 17:43:04 |
| Message-ID: | 200010091743.NAA11909@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
I want to write an admin utility that will view backend SQL queries, and
be able to view locks and statistics using gdb on the running backend.
> "Dale Anderson" <danderso(at)crystalsugar(dot)com> writes:
> > Is there any way to view the locks being held on a table??
>
> There is not any good way --- lock.c has a routine called DumpAllLocks,
> but it's not even compiled by default, let alone connected up to any
> reasonable calling method. I've been thinking for awhile that we
> desperately need some simple way of dumping out the state of the lock
> manager...
>
> regards, tom lane
>
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-10-09 17:52:28 | Re: Table locks |
| Previous Message | Stephan Szabo | 2000-10-09 17:00:34 | Re: Fw: Referencial integrity when there are timestamp primary keys |