Table locking problems?

From: Dan Harris <fbsd(at)drivefaster(dot)net>
To: pgsql-performance(at)postgresql(dot)org
Subject: Table locking problems?
Date: 2005-08-09 18:04:11
Message-ID: 52CFA236-FC43-4018-B399-1854240110FF@drivefaster.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

I thought I would send this to pg-performance since so many people
helped me with my speed issues recently. I was definitely IO-
bottlenecked.

Since then, I have installed 2 RAID arrays with 7 15k drives in them
in RAID 0+1 as well as add a new controller card with 512MB of cache
on it. I also created this new partition on the RAID as XFS instead
of ext3.

These changes have definitely improved performance, but I am now
finding some trouble with UPDATE or DELETE queries "hanging" and
never releasing their locks. As this happens, other statements queue
up behind it. It seems to occur at times of very high loads on the
box. Is my only option to kill the query ( which usually takes down
the whole postmaster with it! ouch ).

Could these locking issues be related to the other changes I made?
I'm really scared that this is related to choosing XFS, but I sure
hope not. How should I go about troubleshooting the "problem"
queries? They don't seem to be specific to a single table or single
database.

I'm running 8.0.1 on kernel 2.6.12-3 on 64-bit Opterons if that
matters..

-Dan

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Rhett Garber 2005-08-09 18:10:33 Re: Why hash join instead of nested loop?
Previous Message Tom Lane 2005-08-09 17:12:59 Re: Why hash join instead of nested loop?