Re: Many processes blocked at ProcArrayLock

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Xiaoyulei <xiaoyulei(at)huawei(dot)com>
Cc: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Many processes blocked at ProcArrayLock
Date: 2014-12-03 13:05:42
Message-ID: 20141203130542.GX1737@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Xiaoyulei wrote:
> I put all the stack in attachment.

Not sure that this is really all that useful. At least I don't have the
patience to examine all this, and I'm not sure it contains the needed
info in the first place. If you were to ensure your build is using
-fno-omit-frame-pointer in cflags and then used "perf record -a -g"
while the test runs and "perf report -g" once it's finished, you'd get a
useful profile that would show who is acquiring the problematic lock and
why.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2014-12-03 13:25:19 Re: About xmllint checking for the validity of postgres.xml in 9.5
Previous Message Alvaro Herrera 2014-12-03 13:00:26 Re: On partitioning