Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ozx7p-0007LW-E6 for pgsql-bugs@arkaria.postgresql.org; Tue, 29 Nov 2022 09:42:01 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ozx7n-0006pS-Mq for pgsql-bugs@arkaria.postgresql.org; Tue, 29 Nov 2022 09:41:59 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ozx7m-0006pC-II for pgsql-bugs@lists.postgresql.org; Tue, 29 Nov 2022 09:41:59 +0000 Received: from wout2-smtp.messagingengine.com ([64.147.123.25]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ozx7j-0001ap-Ft for pgsql-bugs@lists.postgresql.org; Tue, 29 Nov 2022 09:41:57 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 85033320090C; Tue, 29 Nov 2022 04:41:53 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Tue, 29 Nov 2022 04:41:53 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:reply-to:sender :subject:subject:to:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; t=1669714913; x=1669801313; bh=f D7OBxg/cJJObMfjwzciotft3GozBYqb/NgjnkF8YcQ=; b=bn3LPtZ5PCDe+ntA1 Xqugha3/onZxq9sk8sjgVaVFX4ZGppNGjt1djrlpMS7hW5RcMG/Ru6PQPfw4tZGh SdSw5GBSF6zCBZgjsRbqGl1rn3A/TvCLN8f9EWdZG4UgzSRPYPQzkiFc6SGSJjhz e2qfwd1kKLrerD/nRfx/5V6qtCC6HjRk66By5OvSQc5QfRyrjnROKEZieaYEtUyI +zYSiB+TS5kiza9NVteoqNSgh5HzcqFTImIyn3Q6a9cSrET/goIkU0BlAvfjicZ4 nFhWr0Bh4TentUzGYoFJ7PKEuPTbolZw2uUn3x7lyjSt6QYBeZJIN4gpT+qwvrP7 g6D1Q== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvgedrjeeggddtkecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvvefukfggtggugfgjsehtkeertddttdejnecuhfhrohhmpeetlhhvrghr ohcujfgvrhhrvghrrgcuoegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhgqe enucggtffrrghtthgvrhhnpefgtdegleeggffftdeiuddufffhveekgfdufeethefgtefh kedvgeejlefhteehvdenucffohhmrghinhepvghnthgvrhhprhhishgvuggsrdgtohhmpd hpohhsthhgrhgvshhqlhdrohhrghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgr mhepmhgrihhlfhhrohhmpegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhg X-ME-Proxy: Feedback-ID: ia2694551:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 29 Nov 2022 04:41:52 -0500 (EST) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 82D96E98; Tue, 29 Nov 2022 10:41:49 +0100 (CET) Date: Tue, 29 Nov 2022 10:41:49 +0100 From: Alvaro Herrera To: Viljo Hakala Cc: "pgsql-bugs@lists.postgresql.org" Subject: Re: Logical replication halted due to "this slot has been invalidated because it exceeded the maximum reserved size." Message-ID: <20221129094149.zprwiczin3pjicw4@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2022-Nov-29, Viljo Hakala wrote: > We have two PostgreSQL 14.3 on Red Hat Linux 8.5 running two > different databases on VMS, where logical replicationn is used between > databases. Hmm, I don't see any bug fixes in the commit that would match this. I only looked after May 9th 2022, which is 14.3's tag date. > 2022-11-29 10:21:06.940 EET [1698404] ERROR: could not start WAL streaming: ERROR: cannot read from logical replication slot ”logs” > DETAIL: This slot has been invalidated because it exceeded the maximum reserved size. > 2022-11-29 10:21:06.942 EET [1698368] LOG: background worker "logical replication worker" (PID 1698404) exited with exit code 1 > > Even though according to manual the max_slot_wal_keep_size is -1 and should not have a limit ? You should see earlier messages about the slot being invalidated, during the previous checkpoint -- and potentially the walsender being signalled, if it was running. Can you spot those? > postgres=# show max_slot_wal_keep_size; > > max_slot_wal_keep_size > ------------------------ > -1 The only explanation of this behavior that doesn't involve a bug is that this parameter was set to a nonzero value, then set to disabled, but the checkpointer failed to notice the change. -- Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/ "This is what I like so much about PostgreSQL. Most of the surprises are of the "oh wow! That's cool" Not the "oh shit!" kind. :)" Scott Marlowe, http://archives.postgresql.org/pgsql-admin/2008-10/msg00152.php