From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Neo Liu <diabloneo(at)gmail(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #14588: Postgres process blocked on semop |
Date: | 2017-03-12 21:03:12 |
Message-ID: | 20170312210312.5urq2djmdnf4rwlp@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | Postg토토 사이트 추천SQL : Postg토토 사이트 추천SQL 메일 링리스트 : 2017-03-12 이후 PGSQL 버그 21:03 |
Hi,
On 2017-03-12 04:30:52 +0000, Neo Liu wrote:
> *The pstack screenshot*
> It shows two process's stack, one is pid 186397 who were in authentication,
> and the other is 188832 who where in INSERT.
This suggest you're having quite massive contention around
ProcArrayLock. You should consider updating to 9.6. Several releases
since 9.2 considerably improved scalability around this (especially
9.6).
Regards,
Andres
From | Date | Subject | |
---|---|---|---|
Next Message | Venkata B Nagothi | 2017-03-13 00:06:00 | Re: [BUGS] Bug in Physical Replication Slots (at least 9.5)? |
Previous Message | Tom Lane | 2017-03-12 16:30:44 | Re: BUG #14588: Postgres process blocked on semop |