Re: Inconsistent behavior of smart shutdown handling for queries with and without parallel workers

From: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Inconsistent behavior of smart shutdown handling for queries with and without parallel workers
Date: 2020-08-14 05:32:17
Message-ID: CALj2ACUxk6f9Z4K2Pb7NEeMo_Rj4GM4HPs1yJpOhHxrAJRN_5A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I think the inconsistent behaviour reported in this thread gets
resolved with the approach and patch being discussed in [1].

>
> 1. In general, do we need to allow postmaster to send different
> signals to bgworkers for fast and smart shutdowns and let them
> differentiate the two modes(if needed)?
>

Is there any way the bgworkers(for that matter, any postmaster's child
process) knowing that there's a smart shutdown pending? This is
useful, if any of the bgworker(if not parallel workers) want to
differentiate the two modes i.e. smart and fast shutdown modes and
smartly finish of their work.

[1] - https://www.postgresql.org/message-id/469199.1597337108%40sss.pgh.pa.us

With Regards,
Bharath Rupireddy.
EnterpriseDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2020-08-14 06:03:47 Re: Parallel query hangs after a smart shutdown is issued
Previous Message Michael Paquier 2020-08-14 05:25:52 Re: doc examples for pghandler