Re: Add cassert-only checks against unlocked use of relations

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org, Kevin Grittner <kgrittn(at)ymail(dot)com>
Subject: Re: Add cassert-only checks against unlocked use of relations
Date: 2013-11-05 22:03:44
Message-ID: 20131105220344.GM14819@awork2.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2013-11-05 22:35:41 +0100, Andres Freund wrote:
> We could relatively easily optimize that to a constant factor by just
> iterating over the possible lockmodes. Should only take a couple more
> lines.

On that note, any chance you remember why you increased MAX_LOCKMODE by
2 to 10 back in 2001 although AccessExclusiveLock is 8? The relevant
commit is E4fe42dfbc3bafa0ea615239d716a6b37d67da253 .

Greetings,

Andres Freund

--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2013-11-05 22:15:45 Re: UTF8 national character data type support WIP patch and list of open issues.
Previous Message Andres Freund 2013-11-05 21:57:38 Re: Add cassert-only checks against unlocked use of relations