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-10-18 16:54:08 |
Message-ID: | 45365C30.9000008@osdl.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Mark Wong <markw(at)osdl(dot)org> writes:
>> The number of transaction errors increased when I increased the
>> NUM_LOCK_PARTITIONS, which I think is the reason it failed to run when I
>> set it to 16.
>
> Hmm, what sort of errors are we talking about? I wonder if you've
> exposed a bug. Changing NUM_LOCK_PARTITIONS really shouldn't have any
> semantic effect.
The libpq client (error log:
http://dbt.osdl.org/dbt/dbt2dev/results/dev4-015/180/client/error.log)
is saying things like this:
ERROR: too many LWLocks taken
CONTEXT: SQL statement "DELETE FROM new_order
WHERE no_o_id = 2101
AND no_w_id = 349
AND no_d_id = 1"
A grep through that file shows that all the unexpected errors appear to
be due to "too many LWLocks taken".
Mark
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Treat | 2006-10-18 16:59:20 | Re: Hints proposal |
Previous Message | Tom Lane | 2006-10-18 16:47:46 | Re: Lock partitions |