Re: Strange locking choices in pg_shdepend.c - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Strange locking choices in pg_shdepend.c
Date
Msg-id 20080128235909.GE1817@alvh.no-ip.org
Whole thread Raw
In response to Re: Strange locking choices in pg_shdepend.c  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> Decibel! <decibel@decibel.org> writes:
> > Would it be worthwhile to allow for logging when a lock gets upgraded?
> > That would make it easier to protect against deadlocks...
> 
> There is some debug code for that in the backend, but my experience
> is that it's too noisy to have on by default.

Seems a good idea to separate the upgrade bits from the other stuff and
enable it on --enable-cassert or something similar.  TODO for 8.4?

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: [PATCHES] Proposed patch: synchronized_scanning GUCvariable
Next
From: Alvaro Herrera
Date:
Subject: Re: Truncate Triggers