Re: Fwd: How does the partitioned lock manager works?
- From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
- To: rancpine cui <rancpine(at)gmail(dot)com>
- Cc: pgsql-hackers(at)postgresql(dot)org
- Subject: Re: Fwd: How does the partitioned lock manager works?
- Date: Fri, 27 Apr 2007 09:55:24 -0400
- Message-id: <20070427135524.GF4645@alvh.no-ip.org> <text/plain>
rancpine cui escribió:
> I've seen from the README that
> "The shared-memory hash tables for LOCKs and PROCLOCKs are organized
> so that different partitions use different hash chains, and thus there
> is no conflict in working with objects in different partitions."
> What does "hash chains" mean?
Each "hash chain" is a different, separate, independent hash struct.
> As the dynahash.c's "partitioned table" mechanism suggests, a lock's
> bucket number can be calculated from its hash value, then it will be
> inserted into that bucket,so how does partition number works?
Which hash is used depends on the partition number.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Home |
Main Index |
Thread Index