Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rfYDK-000qZX-IS for pgsql-general@arkaria.postgresql.org; Thu, 29 Feb 2024 04:40:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rfYDH-00HY8K-Rv for pgsql-general@arkaria.postgresql.org; Thu, 29 Feb 2024 04:40:08 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rfYDG-00HY8B-Hb for pgsql-general@lists.postgresql.org; Thu, 29 Feb 2024 04:40:08 +0000 Received: from mail03.sge.net ([152.91.27.84]) by magus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rfYDB-001xsn-FG for pgsql-general@lists.postgresql.org; Thu, 29 Feb 2024 04:40:05 +0000 X-IronPort-AV: E=Sophos;i="6.06,192,1705363200"; d="scan'208";a="25343078" Received: from unknown (HELO torino.austrac.gov.au) ([152.91.10.30]) by mail03.sge.net with ESMTP; 29 Feb 2024 04:39:50 +0000 Received: from PDCvSEGDMZM01.localdomain (unknown [172.24.26.103]) by torino.austrac.gov.au (Postfix) with ESMTP id 7C28F81D5E3; Thu, 29 Feb 2024 15:39:50 +1100 (AEDT) DKIM-Filter: OpenDKIM Filter v2.11.0 torino.austrac.gov.au 7C28F81D5E3 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=austrac.gov.au; s=austrac1; t=1709181590; bh=4eDy8tI51ktlKlRG9Zmtn5LjYB3FiuIERFeSOs+e/ME=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=xTgxoSszXZcYbuk/kTKlzxFmRLjS6ATfHPGqfRsMt/yHsFfyJZ49EcfrpRpVK4iTv QYHZd+5HWxD0Z5Z2JrjLEjybqfSiuTdtwQhH7J3r0RwAfgWSafyokhzofA3qjko48M EcrQOuK0G3hPtTQ7Hm6ywHlxSzPQ+RicrDMnKTShKxADqmwVtAOvllYi6eytXoijRl 2xVgrRgBLZXO85orkMniGwDv1oWdUpvBVafYIcoIdSQtSNrtMCq2E9CTK0Ga/fTMAf lMWxCSlTiYbtciTZ1nuiNU1e1XvWoJiOJkqCgs8Yd2MGkpnvmLwBod5KoJfAzBAeqM XegijgNdgnL4Q== Received: from wyla.austrac.gov.au (mailhost11.austrac.gov.au [192.168.90.55]) by PDCvSEGDMZM01.localdomain (MTA) with ESMTP id 4Tldmk0v5wz18p974; Thu, 29 Feb 2024 15:39:50 +1100 (AEDT) Received: from PDCvEX01.hq.austrac.gov.au (PDCvEX01.hq.austrac.gov.au [192.168.81.22]) by wyla.austrac.gov.au (Postfix) with ESMTPS id 1AF58818183; Thu, 29 Feb 2024 15:39:50 +1100 (AEDT) Received: from PDCvEX01.hq.austrac.gov.au (192.168.81.22) by PDCvEX01.hq.austrac.gov.au (192.168.81.22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.6; Thu, 29 Feb 2024 15:39:49 +1100 Received: from PDCvEX01.hq.austrac.gov.au ([fe80::bc49:dbe4:6c26:78b]) by PDCvEX01.hq.austrac.gov.au ([fe80::bc49:dbe4:6c26:78b%6]) with mapi id 15.01.2507.006; Thu, 29 Feb 2024 15:39:49 +1100 From: Mark Schloss To: Kyotaro Horiguchi CC: "pgsql-general@lists.postgresql.org" Subject: RE: walreceiver fails on asynchronous replica [EXTERNAL] [SEC=UNOFFICIAL] Thread-Topic: walreceiver fails on asynchronous replica [EXTERNAL] [SEC=UNOFFICIAL] Thread-Index: AQHaagyweG5/0/znCE+97PMHKnbjvrEgvm5Q Date: Thu, 29 Feb 2024 04:39:49 +0000 Message-ID: References: <7f2cb3a69fe74f9f889aceafcf3906e5@austrac.gov.au> <20240228.150916.2195234979663167268.horikyota.ntt@gmail.com> In-Reply-To: <20240228.150916.2195234979663167268.horikyota.ntt@gmail.com> Accept-Language: en-US, en-AU Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-protective-marking: VER=2018.1, NS=gov.au, SEC=UNOFFICIAL, ORIGIN=mark.schloss@austrac.gov.au x-original-protective-marking: VER=2018.1, NS=gov.au, SEC=UNOFFICIAL, ORIGIN=horikyota.ntt@gmail.com x-janusnet-dialogconfirmed: True x-janusnet-msgid-original: x-janusnet-threadid: x-janusnet-msgid: 1C52B4E5E9F141AA81C4D1F5A76699AE x-janusnet-pmconfirmed: True x-janusnet-classifier: Janusseal for Outlook 3.4.3 x-janusnet-pm-origin: mark.schloss@austrac.gov.au Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 x-msw-jemd-newsletter: false List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk UNOFFICIAL Hello, Thanks for looking at this. I think I complicated things by including barma= n. 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 complete= ly, 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 tha= t the pg_waldump showed the failing lsn was a commit. Thanks UNOFFICIAL -----Original Message----- From: Kyotaro Horiguchi =20 Sent: Wednesday, 28 February 2024 5:09 PM To: Mark Schloss Cc: pgsql-general@lists.postgresql.org Subject: Re: walreceiver fails on asynchronous replica [EXTERNAL] [SEC=3DUN= OFFICIAL] At Wed, 28 Feb 2024 03:23:37 +0000, Mark Schloss wrote in=20 > 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.