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.
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
pgsql-hackers by date
|Next:||From: Andres Freund||Date: 2013-01-12 17:20:34|
|Subject: Re: [PATCH] unified frontend support for pg_malloc et al and
palloc/pfree mulation (was xlogreader-v4)|
|Previous:||From: Amit kapila||Date: 2013-01-12 14:10:45|
|Subject: Re: Performance Improvement by reducing WAL for Update