Re: Lock Modes (Documentation)

From: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, "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 20:13:10
Message-ID: 20051103201310.GZ55520@pervasive.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Nov 02, 2005 at 07:12:36PM -0500, Tom Lane wrote:
> 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).

Ok, so I guess what we really need is just a docs TODO that mentions
LOCK_DEBUG.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Jim C. Nasby 2005-11-03 20:20:26 Re: how to emit line number in a function?
Previous Message Bruce Momjian 2005-11-03 20:13:08 Re: Save prepared plan...