Skip site navigation (1) Skip section navigation (2)

Is it possible to know where is the "deadlock"

From: Arnau <arnaulist(at)andromeiberica(dot)com>
To: PostgreSQL Performance <pgsql-performance(at)postgresql(dot)org>
Subject: Is it possible to know where is the "deadlock"
Date: 2007-07-19 16:44:48
Message-ID: 469F9500.7060402@andromeiberica.com (view raw or flat)
Thread:
Lists: pgsql-performance
Hi all,

   I have a serious problem with a server. This server holds severals 
DB, the problem is thet the CPU's spend most of the time waiting:

Cpu0: 4.0% us, 2.3% sy, 0.0% ni, 61.5% id, 32.1% wa, 0.0% hi, 0.0% si
Cpu1: 2.3% us, 0.3% sy, 0.0% ni, 84.1% id, 13.3% wa, 0.0% hi, 0.0% si
Cpu2: 1.3% us, 0.3% sy, 0.0% ni, 68.6% id, 29.8% wa, 0.0% hi, 0.0% si
Cpu3: 4.6% us, 3.3% sy, 0.0% ni,  2.6% id, 88.4% wa, 0.3% hi, 0.7% si

     The iostat -c says about 8% of time waiting for IO. I'm afraid this 
is due to locks between concurrent queries, is there anyway to have more 
info about?

Thanks all
-- 
Arnau

Responses

pgsql-performance by date

Next:From: Bill MoranDate: 2007-07-19 17:03:26
Subject: Re: Is it possible to know where is the "deadlock"
Previous:From: Josh BerkusDate: 2007-07-19 16:22:24
Subject: Re: User concurrency thresholding: where do I look?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group