From: | Mark Wong <markw(at)osdl(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: Lock partitions |
Date: | 2006-09-11 15:20:35 |
Message-ID: | 45057EC3.7000909@osdl.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
>> I see this in the CVS commits for 8.2. Did we determine the proper
>> number of lock partitions? Should it be based on the number of buffers
>> or concurrent sessions allowed?
>
> No. NUM_LOCK_PARTITIONS needs to be a compile-time constant for a
> number of reasons, and there is absolutely zero evidence to justify
> making any effort (and spending any cycles) on a variable value.
>
> It would be nice to see some results from the OSDL tests with, say, 4,
> 8, and 16 lock partitions before we forget about the point though.
> Anybody know whether OSDL is in a position to run tests for us?
Yeah, I can run some dbt2 tests in the lab. I'll get started on it.
We're still a little bit away from getting the automated testing for
PostgreSQL going again though.
Mark
From | Date | Subject | |
---|---|---|---|
Next Message | Jan de Visser | 2006-09-11 15:22:28 | Re: Proposal for GUID datatype |
Previous Message | Thomas Hallgren | 2006-09-11 15:05:23 | Re: Proposal for GUID datatype |