Jeff Janes <jeff.ja...@gmail.com> writes:
> So my conclusions are:
> 2) Heavy-weight locks are called that for a reason, they use a lot of
> CPU even without contention.
> 3) The CPU usage of the hash-index code proper is quite small, with
> more time being spent in heavy-weight PageLocks (specific to hash
> indexes, but not part of the hash index code itself) and in executor
> code common to all index methods, than in the hash index code.
Interesting. My reaction to that would be to try to replace the
heavyweight locks with LWLocks. IIRC the reason for using heavyweight
locks was fear of deadlocks, but maybe closer analysis and some tweaking
would allow us to eliminate that risk.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
