Re: BUG #14973: hung queries

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Dmitry Shalashov <skaurus(at)gmail(dot)com>, 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:14:05
Message-ID: CAB7nPqTvp5JCXGwr5=zW-WGZOyNjR+yN2G_5Ew-ookBwKAA8Fw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Dec 19, 2017 at 4:02 PM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> 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.

Yeah, that's what happens when calling
WaitForBackgroundWorkerShutdown() as the primary backend waits for all
the workers to stop. You can see it as well this wait event in a
logirep launcher by the way.
--
Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Ashutosh Sharma 2017-12-19 12:00:24 Re: 10.1: hash index size exploding on vacuum full analyze
Previous Message Michael Paquier 2017-12-19 07:10:17 Re: pg_restore --create --no-tablespaces should not issue 'CREATE DATABASE ... TABLESPACE'