Re: Fwd: How does the partitioned lock manager works? - Mailing list pgsql-hackers

From Cui Shijun
Subject Re: Fwd: How does the partitioned lock manager works?
Date
Msg-id 306760850704272310n7b6ca5d9ief224427aece62f8@mail.gmail.com
Whole thread Raw
In response to Re: Fwd: How does the partitioned lock manager works?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Fwd: How does the partitioned lock manager works?  (Heikki Linnakangas <heikki@enterprisedb.com>)
List pgsql-hackers
Ah... It seems that a item is calculated its hash value, get the bucket
number from it and insert into that bucket "chain". The insertion has
nothing to do with partition number(but Alvaro says "which hash is
used depends on the partition number". I haven't really understood
this: how can we get a hash value without deciding which hash to
use? ). However, when we travel along a chain to get a item, we can
infer its partition number from its hash value.

My problem is, I'm not so sure about the process stated above,
because in that way, items in ONE chain may belong to different
partitions,and it is obviously conflicted with " so that different
partitions use different hash chains
" as README mentioned.

2007/4/28, Tom Lane < tgl@sss.pgh.pa.us>:
It's not that hard: the bucket number is some number of low-order bits
of the hash value, and the partition number is some smaller (or at most
equal) number of low-order bits of the hash value.

                        regards, tom lane

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Fwd: How does the partitioned lock manager works?
Next
From: Heikki Linnakangas
Date:
Subject: Re: Fwd: How does the partitioned lock manager works?