Re: Use standard SIGHUP and SIGTERM handlers in autoprewarm module

From: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
To: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
Cc: Craig Ringer <craig(dot)ringer(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Robert Haas <robert(dot)haas(at)enterprisedb(dot)com>
Subject: Re: Use standard SIGHUP and SIGTERM handlers in autoprewarm module
Date: 2020-11-27 07:47:38
Message-ID: CALj2ACUNmtr4NYhOUZGS7KOQCsJXobARiu0YM9M4sgShOpBVdw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Nov 27, 2020 at 12:26 PM Fujii Masao
<masao(dot)fujii(at)oss(dot)nttdata(dot)com> wrote:
>
> > > > When I read the patch again, I found that, with the patch, the shutdown
> > > > of worker_spi causes to report the following FATAL message.
> > > >
> > > > FATAL: terminating connection due to administrator command
> > > >
> > > > Isn't this message confusing because it's not a connection? If so,
> > > > we need to update ProcessInterrupts() so that the proper message is
> > > > reported like other bgworkers do.
> > > >
> > >
> > > This is also true for all the bgworker that use the die() handler. How about doing it the way bgworker_die() does in ProcessInterrupts()? This would give meaningful information. Thoughts? If okay, I can make a separate patch.
> > >
> >
> > Attaching the patch that improved the message for bg workers in ProcessInterrupts(). For instance, now it looks like *FATAL: terminating background worker "worker_spi" due to administrator command* or *FATAL: terminating background worker "parallel worker" due to administrator command *and so on for other bg workers.*
> > *
> >
> > Please review the patch.
>
> Thanks for the patch! It looks good to me.
>

Thanks!

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2020-11-27 07:50:30 Re: Improving spin-lock implementation on ARM.
Previous Message Bharath Rupireddy 2020-11-27 07:46:04 Re: Multi Inserts in CREATE TABLE AS - revived patch