Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gedJz-0007IL-Qy for pgsql-admin@arkaria.postgresql.org; Wed, 02 Jan 2019 10:00:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gedJy-0007aL-IF for pgsql-admin@arkaria.postgresql.org; Wed, 02 Jan 2019 10:00:18 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gedJy-0007aE-11 for pgsql-admin@lists.postgresql.org; Wed, 02 Jan 2019 10:00:18 +0000 Received: from mail-oln040092253096.outbound.protection.outlook.com ([40.92.253.96] helo=APC01-SG2-obe.outbound.protection.outlook.com) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gedJp-00089j-Kp for pgsql-admin@postgresql.org; Wed, 02 Jan 2019 10:00:17 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hotmail.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=RktSICEIezvOytWMxB1PGyOFFKOA1Trv9RTxU3o7/TA=; b=oj9H4iW1gaPfvqu0v/jWs7Hw5oysKM3F4/CcgnUmR9jSvWc3FdDjdzpw1ZGnjizLrbDOOGlCu+Fr9DfxgRPB8zVYN/cOUkTT4BQa+7OPM2J0pJ3FBTks2GXvobmuEjAqIrxa+QOEZ8P7iQC6NpOhdkZh1UsTj3nlQCtMll5hW1bxOLHDN/n7MgOX74MZaMk/8TAVyQrqqdl2OM90ihuiVOLEqzmdZ0s45nzoF9qJLLtSHIF0UsNE82JWNo6FgiuVGXlVDRKEFtEkg6otc2yq3AvAvLhgBMBouGRYhOy0IkTr7YmQdgUpUHHaOyNqxYLnMDewSBSsQRdpthaUS+Fy+Q== Received: from HK2APC01FT060.eop-APC01.prod.protection.outlook.com (10.152.248.53) by HK2APC01HT071.eop-APC01.prod.protection.outlook.com (10.152.248.229) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1471.13; Wed, 2 Jan 2019 10:00:04 +0000 Received: from MA1PR0101MB1687.INDPRD01.PROD.OUTLOOK.COM (10.152.248.59) by HK2APC01FT060.mail.protection.outlook.com (10.152.249.160) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1471.13 via Frontend Transport; Wed, 2 Jan 2019 10:00:04 +0000 Received: from MA1PR0101MB1687.INDPRD01.PROD.OUTLOOK.COM ([fe80::6485:aa94:bdb0:92c3]) by MA1PR0101MB1687.INDPRD01.PROD.OUTLOOK.COM ([fe80::6485:aa94:bdb0:92c3%8]) with mapi id 15.20.1471.019; Wed, 2 Jan 2019 10:00:04 +0000 From: soumitra bhandary To: rajan , "pgsql-admin@postgresql.org" Subject: Re: Is there any way that one of the Postgres Background/Utility process may go down? Thread-Topic: Is there any way that one of the Postgres Background/Utility process may go down? Thread-Index: AQHUooF1+4MvsTh/fEWKuuM9pc+yU6WbvgpP Date: Wed, 2 Jan 2019 10:00:04 +0000 Message-ID: References: <1546422981227-0.post@n3.nabble.com> In-Reply-To: <1546422981227-0.post@n3.nabble.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-incomingtopheadermarker: OriginalChecksum:3CD2F0A9CF8AB646F9BF4E581854467D6DED67127440BE8CE40ED8B445E226EC;UpperCasedChecksum:BD6FFD26BC65ECD9A76898B9C9F1D0DDAE5A89D2A033737F7367F4545B3F0A76;SizeAsReceived:7144;Count:46 x-ms-exchange-messagesentrepresentingtype: 1 x-tmn: [0y9GLhSxLag4FbQGEL9sb+NPIzW9qGz7] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1;HK2APC01HT071;6:yWH9BKNL1CXVZnpa5Cc19HtH2lZNT82TjQDLP0W0bWxm1ZtQu94lajG+4JUfSPJpelWWxfIaLkz4jCohTjZ/HFMYDMChX2YAyKzwFOctsVaFUoIP81upj+wNpSxLPST/w+E7Gfdjac9KkDW6gK/mvAxOrt9H/x8xXy3gLQ7LmwJwRG8q8TY/6SWh8bsi0MGgXVxQvLA3RN9n4vrZTFUeIiiIZ1G/ri0+yd1i364XgOfWJdYzbh8r2mQOvFIkwP9MUu4ASDMdQlCEC/pKuzjcTrEhNaXwLfhjO9uMjsCgIySeMDhfAav7KXfKmxflRcYItNvs1a/fiBLdzPaiE97eH9LucwNGNKSOy7zR2PI8Fw3D5quGGn6BL6WU8jAeQ1KrAxA2gBYUwc0kltZB69UFtBLy6BO0tTgLrSaHVyXBuHXZ4EAAoKjulH4oZ7s7dru0w26BrvWUW0lVW6zp1YIbkw==;5:6pwyI5MYJ4mgp28z6wV8yKpWJttESftPjLU+Vwa81zvz5HWtgc251qPWMxrao7m9FwUQBIHzKwYtVtbvuoPJ0c1dot4oiGH0b6A2vsR3YMOjyuReYDloNLdoQ2B1PsIa1PXcZXNskGfyDH6SVGoRbNTVz6v+rAY1pZ62JBvySPI=;7:bk7rNmzpSHG6GmKX87sk+7T+VBwnJIEk3C6qq0F7+JC8tB1izoz+0HY/nC+//bcslm5yUwJ4LCxdGOzc25yCPsz1zQxW4hD1M1XYO897BEYfI6oXYR08otvmXVP3y+lERIS3LOYSCA9taatAdHnU3Q== x-incomingheadercount: 46 x-eopattributedmessage: 0 x-microsoft-antispam: BCL:0;PCL:0;RULEID:(2390118)(7020095)(20181119063)(201702061078)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031323274)(2017031324274)(2017031322404)(1601125500)(1603101475)(1701031045);SRVR:HK2APC01HT071; x-ms-traffictypediagnostic: HK2APC01HT071: x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:(4566010)(82015058);SRVR:HK2APC01HT071;BCL:0;PCL:0;RULEID:;SRVR:HK2APC01HT071; x-microsoft-antispam-message-info: 3ocZSLnQE2a6J2ky5/w4r5kZBqaQoC7hspuEVTh2FkuJTgRcDJAMUhkchLfOqVys Content-Type: multipart/alternative; boundary="_000_MA1PR0101MB1687CD583F1DA7EB6E8C66F9E08C0MA1PR0101MB1687_" MIME-Version: 1.0 X-OriginatorOrg: hotmail.com X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 7181d4b0-87d6-4f4e-ba33-0d3746212cec X-MS-Exchange-CrossTenant-Network-Message-Id: 00eb65a5-65b8-471b-678c-08d6709911a2 X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 7181d4b0-87d6-4f4e-ba33-0d3746212cec X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Jan 2019 10:00:04.6986 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Internet X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-Transport-CrossTenantHeadersStamped: HK2APC01HT071 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --_000_MA1PR0101MB1687CD583F1DA7EB6E8C66F9E08C0MA1PR0101MB1687_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi , If wal sender process exceeds the max_wal_sender_timeout parameter value , = it might stop sending the wal to the slave nodes . But will not die out . I= n this case you may notice no change in the wal location associated with wa= l sender process . Please refer to the Postgres log for exact issue . Thanks, Soumitra ________________________________ From: rajan Sent: Wednesday, January 2, 2019 3:26 PM To: pgsql-admin@postgresql.org Subject: Is there any way that one of the Postgres Background/Utility proce= ss may go down? Is there any way that one of the Postgres Background process may go down? meaning the process getting stopped? For example, can the wal sender process alone stop working? If it does so, which part of the logs I must check to proceed further. ----- -- Thanks, Rajan. -- Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html --_000_MA1PR0101MB1687CD583F1DA7EB6E8C66F9E08C0MA1PR0101MB1687_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi , 

If wal sender process exceeds the max_wal_sender_timeout parameter value , = it might stop sending the wal to the slave nodes . But will not die out . I= n this case you may notice no change in the wal location associated with wa= l sender process . 
Please refer to the Postgres log for exact issue . 

Thanks, 
Soumitra 


From: rajan <vgmonnet@gm= ail.com>
Sent: Wednesday, January 2, 2019 3:26 PM
To: pgsql-admin@postgresql.org
Subject: Is there any way that one of the Postgres Background/Utilit= y process may go down?
 
Is there any way that one of the Postgres Backgrou= nd process may go down?
meaning the process getting stopped?

For example, can the wal sender process alone stop working? If it does so, =
which part of the logs I must check to proceed further.



-----
--
Thanks,
Rajan.
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html

--_000_MA1PR0101MB1687CD583F1DA7EB6E8C66F9E08C0MA1PR0101MB1687_--