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.96) (envelope-from ) id 1vcT1a-006xhi-1m for pgsql-admin@arkaria.postgresql.org; Sun, 04 Jan 2026 18:40:23 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vcT1X-00FoJZ-16 for pgsql-admin@arkaria.postgresql.org; Sun, 04 Jan 2026 18:40:20 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vcT1W-00FoJQ-0t for pgsql-admin@lists.postgresql.org; Sun, 04 Jan 2026 18:40:19 +0000 Received: from fhigh-a8-smtp.messagingengine.com ([103.168.172.159]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vcT1V-004Aba-0Z for pgsql-admin@lists.postgresql.org; Sun, 04 Jan 2026 18:40:17 +0000 Received: from phl-compute-03.internal (phl-compute-03.internal [10.202.2.43]) by mailfhigh.phl.internal (Postfix) with ESMTP id 71A1714000C5; Sun, 4 Jan 2026 13:40:15 -0500 (EST) Received: from phl-frontend-03 ([10.202.2.162]) by phl-compute-03.internal (MEProxy); Sun, 04 Jan 2026 13:40:15 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= quadratum-braccas.com; h=cc:content-transfer-encoding :content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm1; t=1767552015; x=1767638415; bh=1FRZEJyTcL CObc+IhTz//r5hQYfuiaq8jTJQs73cmag=; b=MMNSuISCH/Qx3ZBP2XOo2rZBQg V720uScdy/Tspk8euqMQ9W7+BENP6hheVzdx1vAWIOyN4UhaR6gOrgYLpgK0Tv/b UAn7wvjAUDnsMdUbU9Sj+Ov5pbE1/2tnyX5ORK0PU93mLRaCQBVsRC3WDiccz7YY exW4a5azyU6VYHdnIlYS4KbAzFK6UM1fZ/89EQGmsMZSMg3nqdHyQCAbiAPZYU2I qo1cNcWEwbClbz4IExkt55VQ9PFUrHueXYRv1eyEORnFouyhHm9eFgiRCyPH332F k6H5sVjf3Ra/AMnDqg9BeIWrNhI1eCy3/L8JaoZc5JZSZGfKzS+C39m3omgg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; t=1767552015; x=1767638415; bh=1 FRZEJyTcLCObc+IhTz//r5hQYfuiaq8jTJQs73cmag=; b=S+qMBpZ06/c+CYOqJ k20f6si6Bxu5Yzwze6O/aMcyhgrjg3VKIrd/pQvC5b5BdrvOi7gKGCuyzOqOCIMG lB1Gnr8UcoMShyqtu/3cWOMO9MsMntcnmg2X13Xf7RY0OTX08MRD9CZdLijy8onR GIGyrEw9ndz8FtMAbUsAYebs6ZAdKRbgdccYaplTat+MFUbcnxU2tEPeOVlM4RN9 nCw67WnE9qObriJsMK4TB3fWdhDPM0U6g/+2SSYF2IYtMKsAHw/0VLd+WkG6Q1Sb EcTrW0HtQo78X2/IOPz1wMQftETxx1eX4uGixJPdgTzOtn9u6Iv1t99ytR7R98FQ 3FKfQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefgedrtddtgdelhedujecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpuffrtefokffrpgfnqfghnecuuegr ihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjug hrpefkffggfgfuvfhfhfgjtgfgsehtkeertddtvdejnecuhfhrohhmpefusghosgcuoehs sghosgesqhhurggurhgrthhumhdqsghrrggttggrshdrtghomheqnecuggftrfgrthhtvg hrnhepgeejgedtudehtdehudefkeejveeftdeludffudevleetkeefleffleetfefffffh necuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepshgsoh gssehquhgrughrrghtuhhmqdgsrhgrtggtrghsrdgtohhmpdhnsggprhgtphhtthhopeef pdhmohguvgepshhmthhpohhuthdprhgtphhtthhopehlrghurhgvnhiirdgrlhgsvgestg ihsggvrhhtvggtrdgrthdprhgtphhtthhopehpghhsqhhlqdgrughmihhnsehlihhsthhs rdhpohhsthhgrhgvshhqlhdrohhrghdprhgtphhtthhopehssghosgesqhhurggurhgrth humhdqsghrrggttggrshdrtghomh X-ME-Proxy: Feedback-ID: i374947ac:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 4 Jan 2026 13:40:14 -0500 (EST) Message-ID: Date: Sun, 4 Jan 2026 11:40:13 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: struggling with logical replication and WAL segments removed even with max_slot_wal_keep_size = -1 To: Laurenz Albe , pgsql-admin@lists.postgresql.org References: <82666d95c1c837ce600bc2a3f212f8ebbc1f5b22.camel@cybertec.at> Content-Language: en-US From: Sbob In-Reply-To: <82666d95c1c837ce600bc2a3f212f8ebbc1f5b22.camel@cybertec.at> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 1/4/26 9:29 AM, Laurenz Albe wrote: > On Sat, 2026-01-03 at 11:28 -0700, Sbob wrote: >> we have been fighting logical replication for some timetgres v14, >> max_slot_wal_keep_size = -1 but I still get this kind of error on the >> publisher every few days: >> >> ERROR:  requested WAL segment 00000002000009D6000000AB has already been removed > What is the "wal_status" of the replication slot in "pg_replication_slots"? > > Unless you are hitting a bug (what is you minor version?), I'd say that some > rogue software is removing files from "pg_wal". > > Compare the "restart_lsn" from "pg_replication_slots" with the available > WAL segments on the primary. > > Yours, > Laurenz Albe We are running version 14.19 I will check the wal status next time this happens Thanks