Subject: Re: Immediate Shutdowns
To: Harold Falkmeyer <hfalkmeyer@gmail.com>, pgsql-admin@postgresql.org
References: 
 <CACcYrisGrexO5SkHL++UVQ3VEgPe5UzGK4nC9R_JCmOuyfFRyg@mail.gmail.com>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Organization: 2ndQuadrant
Message-ID: <bde871fb-f410-d162-a0f9-104e3aae4dd2@2ndquadrant.com>
Date: Tue, 6 Jun 2017 23:25:04 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0)
 Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: 
 <CACcYrisGrexO5SkHL++UVQ3VEgPe5UzGK4nC9R_JCmOuyfFRyg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

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


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin