From: Mark Schloss <Mark.Schloss@austrac.gov.au>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
Subject: RE: walreceiver fails on asynchronous replica [EXTERNAL] [SEC=UNOFFICIAL]
Date: Thu, 29 Feb 2024 04:39:49 +0000
Message-ID: <ad7c834f4daa4aa4a53559267ff30eda@austrac.gov.au> (raw)
In-Reply-To: <20240228.150916.2195234979663167268.horikyota.ntt@gmail.com>
References: <7f2cb3a69fe74f9f889aceafcf3906e5@austrac.gov.au>
<20240228.150916.2195234979663167268.horikyota.ntt@gmail.com>
UNOFFICIAL
Hello,
Thanks for looking at this. I think I complicated things by including barman. I was just wanting to point out each primary streams to two locations - the walreceiver on the replica and the walreciver used by barman. We think the reason the barman WAL-receiver didn't fail is because there is no apply of the WAL in Barman but the Standby is applying and it's WAL-receiver got terminated, so the barman server can be taken out of this picture completely, they were just there as a by-product in trying to determine the effect. We are only interested in the killing of the standby wal-receiver and that the pg_waldump showed the failing lsn was a commit.
Thanks
UNOFFICIAL
-----Original Message-----
From: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Sent: Wednesday, 28 February 2024 5:09 PM
To: Mark Schloss <Mark.Schloss@austrac.gov.au>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: walreceiver fails on asynchronous replica [EXTERNAL] [SEC=UNOFFICIAL]
At Wed, 28 Feb 2024 03:23:37 +0000, Mark Schloss <Mark.Schloss@austrac.gov.au> wrote in
> Thank you for your reply. I can confirm there were no changes made to the config of the replica.
Okay.
> Is there any significance in the parameters in the commit record -
> 'inval msgs: catcache 21; sync'.
I think it is not relevant.
> - The walreceiver on the barman server did not fail but the WAL file does not contain the commit transaction
I don't have detailed knowledge of barman's behavior, but it seems to
be quite normal for barman to write out only on receiving a commit
record. What I don't understand here is how those WAL files on the
barman server are related to the failed replicas.
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: Mark.Schloss@austrac.gov.au, horikyota.ntt@gmail.com
Subject: Re: walreceiver fails on asynchronous replica [EXTERNAL] [SEC=UNOFFICIAL]
In-Reply-To: <ad7c834f4daa4aa4a53559267ff30eda@austrac.gov.au>
References: <7f2cb3a69fe74f9f889aceafcf3906e5@austrac.gov.au> <20240228.150916.2195234979663167268.horikyota.ntt@gmail.com> <ad7c834f4daa4aa4a53559267ff30eda@austrac.gov.au>
* 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