From: Achilleas Mantzios <achill@matrix.gatewaynet.com>
To: pgsql-admin@lists.postgresql.org
Subject: Logical wal receiver (background worker) not detecting when publisher node has died
Date: Fri, 23 Nov 2018 07:20:51 +0200
Message-ID: <cd6ba6d5-d76d-4a69-a743-00544ec2dbca@matrix.gatewaynet.com> (raw)
Dear List,
Coming back from :
https://www.postgresql.org/message-id/ae8812c3-d138-73b7-537a-a273e15ef6e1%40matrix.gatewaynet.com
and having got absolutely no helpful answer from our infrastructure
people, I would like to ask :
Is it on earth possible that the primary (publisher node) has crushed
while on the subscriber node the logical wal receiver goes on happily
like there is no problem at all, no messages in log, no timeouts, acts
if nothing happen ?
(in the meantime the second standby instantly detected the crush of the
primary and immediately restarted re-connection attempts)
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: achill@matrix.gatewaynet.com, pgsql-admin@lists.postgresql.org
Subject: Re: Logical wal receiver (background worker) not detecting when publisher node has died
In-Reply-To: <cd6ba6d5-d76d-4a69-a743-00544ec2dbca@matrix.gatewaynet.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