Skip site navigation (1) Skip section navigation (2)

Re: Strange locking choices in pg_shdepend.c

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Decibel! <decibel(at)decibel(dot)org>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Strange locking choices in pg_shdepend.c
Date: 2008-01-28 23:59:09
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Tom Lane wrote:
> Decibel! <decibel(at)decibel(dot)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                      
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2008-01-29 00:09:13
Subject: Re: Truncate Triggers
Previous:From: Caleb WeltonDate: 2008-01-28 23:57:40
Subject: Transition functions for SUM(::int2), SUM(::int4, SUM(::int8])

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group