| From: | Neo Liu <diabloneo(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #14588: Postgres process blocked on semop |
| Date: | 2017-03-13 02:36:41 |
| Message-ID: | CAF_Sdb_eei4ofiBTkV_V1XQGw7fdYM6dVhRckszXeC6FFjg61g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Mar 13, 2017 at 12:30 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-03-13 06:51:47 | Re: BUG #14586: Permissions of recovery.conf are different in plain and tar-format |
| Previous Message | Neo Liu | 2017-03-13 02:29:43 | Re: BUG #14588: Postgres process blocked on semop |