| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Dmitry Shalashov <skaurus(at)gmail(dot)com> |
| Cc: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #14973: hung queries |
| Date: | 2017-12-19 07:02:04 |
| Message-ID: | CAA4eK1LD0JOxYwNEAmLeNCVPK0yPN68cY8tgWuDx-N5ayLMVSg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Dec 19, 2017 at 2:48 AM, Dmitry Shalashov <skaurus(at)gmail(dot)com> wrote:
> Hi Thomas,
>
> I'm glad to help. Thanks for the advice!
>
> By the way, there was a mistake in my bug report - wait_event actually was
> BgWorkerShutdown.
>
I think BgWorkerShutdown type of wait event can be only for the master
backend not for all the workers. Are there any other wait events?
Can we get a stack trace of one or more workers?
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-12-19 07:10:17 | Re: pg_restore --create --no-tablespaces should not issue 'CREATE DATABASE ... TABLESPACE' |
| Previous Message | Bossart, Nathan | 2017-12-18 22:18:09 | Re: BUG #14941: Vacuum crashes |