| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, "Thomas F(dot) O'Connell" <tfo(at)sitening(dot)com>, PgSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Lock Modes (Documentation) |
| Date: | 2005-11-03 00:12:36 |
| Message-ID: | 14842.1130976756@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Jim C. Nasby wrote:
>> Would it be feasable to have the lock manager spew out info about lock
>> aquisition and release? Not only would it make getting this information
>> easy, but I suspect it could be a useful debugging tool.
> Something like log_locks? That would be valuable.
A moment's thought would suggest that the output would be too voluminous
to be of any use whatever to ordinary users. The capability already
exists at the developer level (see LOCK_DEBUG).
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Trent Shipley | 2005-11-03 00:26:56 | FOSS Reporting tools (was Oracle 10g Express - any danger for Postgres?) |
| Previous Message | Matthew Terenzio | 2005-11-03 00:09:00 | Re: SQL injection |