Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dkEfX-0002ut-Oc for pgsql-admin@arkaria.postgresql.org; Tue, 22 Aug 2017 19:16:55 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dkEfX-000489-66 for pgsql-admin@arkaria.postgresql.org; Tue, 22 Aug 2017 19:16:55 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dkEfV-00047Z-Rm for pgsql-admin@postgresql.org; Tue, 22 Aug 2017 19:16:54 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dkEfS-0002i1-Px for pgsql-admin@postgresql.org; Tue, 22 Aug 2017 19:16:52 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 8AE9E21673; Tue, 22 Aug 2017 15:16:49 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Tue, 22 Aug 2017 15:16:49 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=9UG8ucVdINSBHON4yZTGTh4rgy8BOzzuSd/SphnuQ2o=; b=IUntShbE rLClM1wiFBevPZ9+5b7UySeqow+vrMMusWORNk/98VGTHsPi++JHOMBtbqxRz3/P GcnCC7L3XvEn+9L9m/TliY5lTLZq9nloGT4bziS1Uu0RgkBRtiZuMmJtr9IYMQrT 7NyuBCNF0nsLmTvhg9Q2riBTyQ8YhQnInd/kgINPfT35EW3al6z/aNcmWoRt0JIC nIG2aImvz09vcz2GLmwQ9+gmuqz30LqwyExuL6jlWTkSNnO7prSIDbyI7DYOoCS2 HstCpyNyo02qRz8tx2AxIQ2ZU39oT7dYjPpF5Le9a5ECVkFbA3hascARzCHmhDKb 5DyQSPO2xHO4gg== X-ME-Sender: X-Sasl-enc: fIaKd6TBpb1Fl5uV7E6i5/QaPXCJxKt9q6RqQePQ+heu 1503429409 Received: from april.local (c-73-13-66-39.hsd1.pa.comcast.net [73.13.66.39]) by mail.messagingengine.com (Postfix) with ESMTPA id 47EC3240AF; Tue, 22 Aug 2017 15:16:49 -0400 (EDT) Subject: Re: PostgreSQL 9.4.13 is facing issue in shutting down To: Abhijit Gharami , pgsql-admin@postgresql.org References: From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: <9e38a778-1988-3eac-acbe-822f4dad9722@2ndquadrant.com> Date: Tue, 22 Aug 2017 15:16:48 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org On 8/21/17 06:26, Abhijit Gharami wrote: > Recently we have updated our PostgreSQL version from 9.4.12 to 9.4.13. > With version 9.4.13 while trying to stop the PostgreSQL server, database > is facing issues in shutting down. The problem probably occurs because > of the WAL sender process not getting terminated on shutdown request.  This is probably the same issue as reported here: https://www.postgresql.org/message-id/1434ad79-ab0d-d6a9-4ea2-1afb1c06adaf%402ndquadrant.it You can try the patch attached there, or downgrade to 9.4.12 while this issue is being investigated. -- 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