Re: Lock Modes (Documentation)

From: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: "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:11:40
Message-ID: 20051103201140.GY55520@pervasive.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Nov 02, 2005 at 06:30:38PM -0500, Bruce Momjian wrote:
> Jim C. Nasby wrote:
> > On Wed, Nov 02, 2005 at 05:59:15PM -0500, Bruce Momjian wrote:
> > > Actually, pre-8.1 used ROW EXCLUSIVE for foreign keys because we didn't
> > > have ROW SHARE until 8.1. I actually can't find out how we are doing
> > > that in the code, however. Analyzing the code is probably the only way
> > > to get this detailed lock information.
> >
> > 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.

Maybe you should ask the keeper of the TODO to add it... ;P
--
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 Bruce Momjian 2005-11-03 20:13:08 Re: Save prepared plan...
Previous Message Richard_D_Levine 2005-11-03 20:03:02 Re: OT It is here: Oracle 10g Express