| 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: | 20080128235909.GE1817@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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 http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2008-01-29 00:09:13 | Re: Truncate Triggers |
| Previous Message | Caleb Welton | 2008-01-28 23:57:40 | Transition functions for SUM(::int2), SUM(::int4, SUM(::int8]) |