Re: [RFC] Should we fix postmaster to avoid slow shutdown? - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [RFC] Should we fix postmaster to avoid slow shutdown?
Date
Msg-id CA+TgmoYcMBi3RdSUpW6t6PN-7u7PWMNNa02VWUQVFNH9-vEHAQ@mail.gmail.com
Whole thread Raw
In response to Re: [RFC] Should we fix postmaster to avoid slow shutdown?  (Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>)
Responses Re: [RFC] Should we fix postmaster to avoid slow shutdown?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Oct 26, 2016 at 7:12 AM, Ashutosh Bapat
<ashutosh.bapat@enterprisedb.com> wrote:
> Also, many other SIGQUIT handlers like bgworker_quickdie() call on_exit_reset()
> followed by exit(2) instead of just exit(1) in pgstat_quickdie(). Why is this
> difference?

Well, for that, you'd need to look at how postmaster.c treats those
exit codes.  exit(2) from a regular backend or background worker will
cause a crash-and-restart cycle; I'm not sure whether the handling for
the stats collector is similar or different.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Rename max_parallel_degree?
Next
From: Kuntal Ghosh
Date:
Subject: Re: [bug fix] Stats collector is not restarted on the standby