On Sat, Jan 12, 2013 at 11:39 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> Lock code says it calculates "hash value once and then pass around as needed".
> But it actually calculates it twice for new locks.
> Trivial patch attached to make it follow the comments in
> LockTagHashCode and save a few cycles.
Hmm. This is a nice idea, but it doesn't look right to me, because
you're searching LockMethodLocalHash with a hash code intended to be
used in LockMethodLockHash, and the two hashing schemes are not
compatible, because the former is hashing a LOCALLOCKTAG, and the
latter is hashing a LOCKTAG, and both are just using tag_hash.
On the flip side if I'm wrong and the hashing schemes are compatible,
there are other places in the file where the same trick could be
The Enterprise PostgreSQL Company
In response to
- Hash twice at 2013-01-12 16:39:15 from Simon Riggs
pgsql-hackers by date
|Next:||From: Simon Riggs||Date: 2013-01-14 19:50:43|
|Subject: Re: Hash twice|
|Previous:||From: Alvaro Herrera||Date: 2013-01-14 19:07:29|
|Subject: Re: erroneous restore into pg_catalog schema|