From: soumitra bhandary <soumitra.bhandary@hotmail.com>
To: rajan <vgmonnet@gmail.com>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Is there any way that one of the Postgres Background/Utility process may go down?
Date: Wed, 2 Jan 2019 10:00:04 +0000
Message-ID: <MA1PR0101MB1687CD583F1DA7EB6E8C66F9E08C0@MA1PR0101MB1687.INDPRD01.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <1546422981227-0.post@n3.nabble.com>
References: <1546422981227-0.post@n3.nabble.com>
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 . In this case you may notice no change in the wal location associated with wal sender process .
Please refer to the Postgres log for exact issue .
Thanks,
Soumitra
________________________________
From: rajan <vgmonnet@gmail.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/Utility process 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: soumitra.bhandary@hotmail.com, vgmonnet@gmail.com
Subject: Re: Is there any way that one of the Postgres Background/Utility process may go down?
In-Reply-To: <MA1PR0101MB1687CD583F1DA7EB6E8C66F9E08C0@MA1PR0101MB1687.INDPRD01.PROD.OUTLOOK.COM>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox