Re: [BUGS] BUG #14588: Postgres process blocked on semop - Mailing list pgsql-bugs

From Neo Liu
Subject Re: [BUGS] BUG #14588: Postgres process blocked on semop
Date
Msg-id CAF_Sdb_eei4ofiBTkV_V1XQGw7fdYM6dVhRckszXeC6FFjg61g@mail.gmail.com
Whole thread Raw
In response to Re: [BUGS] BUG #14588: Postgres process blocked on semop  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs


On Mon, Mar 13, 2017 at 12:30 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:


Which of those would the stuck processes be using?

Also, can you attach to a few of the stuck processes and get stack traces?

https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend

                        regards, tom lane

Hi, Tome

I can't get stack traces for you now. We already add a cron job to restart the pgsql server every morning to solve the problem temporarily. It's a production system in client's environment, I can't login into the system now.

I hope the pstack output in early message can help you.

Thanks, diabloneo

pgsql-bugs by date:

Previous
From: Neo Liu
Date:
Subject: Re: [BUGS] BUG #14588: Postgres process blocked on semop
Next
From: Michael Paquier
Date:
Subject: Re: [BUGS] BUG #14586: Permissions of recovery.conf are different inplain and tar-format