| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Harold Falkmeyer <hfalkmeyer(at)gmail(dot)com>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Immediate Shutdowns |
| Date: | 2017-06-07 03:25:04 |
| Message-ID: | bde871fb-f410-d162-a0f9-104e3aae4dd2@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On 6/6/17 22:56, Harold Falkmeyer wrote:
> Are there long-term detriments from executing an immediate shutdown
> and/or issuing SIGQUITs to either the parent or any child postmaster?
There shouldn't be any.
> What might cause an operation, such as a VACUUM ANALYZE, not to exit
> upon receiving a SIGTERM. Are there any circumstances when a SIGQUIT
> could fail to cause an imminent exit (other than a process in an
> fundamentally unreceptive state, such as an uninterruptible sleep).
You write in another thread that you are using 8.4. That could
certainly have more issues/bugs in this area, if you're not seeing the
behavior you want.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | x_hsky | 2017-06-07 04:06:31 | PG 10.0 Distributed Configuration |
| Previous Message | Harold Falkmeyer | 2017-06-07 02:56:24 | Immediate Shutdowns |