Fwd: How does the partitioned lock manager works?

From: "rancpine cui" <rancpine(at)gmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Fwd: How does the partitioned lock manager works?
Date: 2007-04-27 13:32:25
Message-ID: 306760850704270632k4968e6a8i94de637b52a94f99@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

---------- Forwarded message ----------
From: rancpine cui <rancpine(at)gmail(dot)com>
Date: 2007-4-27 下午9:22
Subject: Re: [HACKERS] How does the partitioned lock manager works?
To: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>

Thanks for your reply. :-)
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?
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?
Is it only a flag which suggests the partition the lock belongs to when
we want to use that lock? I can't find a way to manage locks via
partition...

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2007-04-27 13:55:24 Re: Fwd: How does the partitioned lock manager works?
Previous Message Chris Browne 2007-04-27 13:30:27 Re: Modifying TOAST thresholds