| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com> |
| Cc: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [RFC] Should we fix postmaster to avoid slow shutdown? |
| Date: | 2016-10-26 12:27:41 |
| Message-ID: | CA+TgmoYcMBi3RdSUpW6t6PN-7u7PWMNNa02VWUQVFNH9-vEHAQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Oct 26, 2016 at 7:12 AM, Ashutosh Bapat
<ashutosh(dot)bapat(at)enterprisedb(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kuntal Ghosh | 2016-10-26 12:41:34 | Re: [bug fix] Stats collector is not restarted on the standby |
| Previous Message | Robert Haas | 2016-10-26 12:24:33 | Re: Rename max_parallel_degree? |