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 1sFbK5-003qSC-CI for pgsql-general@arkaria.postgresql.org; Fri, 07 Jun 2024 15:16:10 +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 1sFbK3-00Clae-Pe for pgsql-general@arkaria.postgresql.org; Fri, 07 Jun 2024 15:16: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 1sFbK3-00ClaU-E0 for pgsql-general@lists.postgresql.org; Fri, 07 Jun 2024 15:16:08 +0000 Received: from wfhigh5-smtp.messagingengine.com ([64.147.123.156]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sFbJw-000Tjz-Mz for pgsql-general@lists.postgresql.org; Fri, 07 Jun 2024 15:16:07 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailfhigh.west.internal (Postfix) with ESMTP id 7F03418000AB; Fri, 7 Jun 2024 11:15:57 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Fri, 07 Jun 2024 11:15:57 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc: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=fm3; t=1717773357; x=1717859757; bh=DJB1xWa4p3W+0L/4A3XlSXnqIGL2OJuosrbn2RLuDd4=; b= NbycZd6pILv3oQ9vGMzzHeEscunurseYf/S3TMnTV2jQOlMjwRPRRAN67OScQ2Kv mTUQ7XfwTiYcI6sTYvgNMyj9+qhO2hGKNdbLIRcUevjEDPxU2QfvEJ1KIEPW6RLn nWG/jevfRIkaQEMRz20uPAYnYoz0UNMNU9m3Sp60BUxSxAt9K4ozqm0hYGLo8Qud P/1sfsSOgosTR/VkIh00y7xow00YjacR+53+CtCPjakQ2rxjKcUFGaHv6DPY7UT8 eFTAw3dX9i9aV+6KhYSgB431fGqFRkwNYLnD4+BXfh/eVS/wGxtZrNNYfai1q3GD EFcCfii9wEJa5eGcL1TqsQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1717773357; x= 1717859757; bh=DJB1xWa4p3W+0L/4A3XlSXnqIGL2OJuosrbn2RLuDd4=; b=V pHjttpt7z//mfQJIKyPzkWEkL02MgyHVy94gMh9rqXylgGz0QEoVKsl4uf2c78s4 7J9kZxVsHN2639Gmbeb8s3HDc2T+TZbQcwVHss254T8ESua1GbHLVOdvvqmpI/Vg nr5Du9EYjGbzAAOdIoKK6iPdXQQhYmHWnhd7RqD8evVZLLD2M9ZP2n7Ehp7dXHXj f5uU4JJUUsSeJiWFvjrbvzCm+gaSFKhQ0JMUoiY/juDcfyA3Cr/QW75Qi/msHsVK +wr+++ra/aae5J5Kc3V8W8+E7oTtByl3ubAzv1pRrni5Yii2M3Sp8dsDRVG9Qd+L jAwxxADsejc15mKbICuSQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrfedtuddgiedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvvehfhfgjtgfgsehtjeertddtvdejnecuhfhrohhmpeetughr ihgrnhcumfhlrghvvghruceorggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtg homheqnecuggftrfgrthhtvghrnhepuedufeejjefggfdttdeghefgkeeuveekkeeiteet tdekffehiedvtefhveffgeeunecuffhomhgrihhnpehpohhsthhgrhgvshhqlhdrohhrgh enucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrughr ihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtohhm X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 7 Jun 2024 11:15:56 -0400 (EDT) Message-ID: <490e8a5c-f1f5-40fe-8243-f1c8c18d03f2@aklaver.com> Date: Fri, 7 Jun 2024 08:15:56 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Questions on logical replication To: Koen De Groote Cc: PostgreSQL General References: <1628637f-419f-4f6a-9cb6-07af90cd0bc4@aklaver.com> <1c0273f5-a90a-48f6-b51f-fe15c16fa1c6@aklaver.com> Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 6/6/24 15:19, Koen De Groote wrote: > I'll give them a read, though it might take a few weekends > > Meanwhile, this seems to be what I'm looking for: > > From > https://www.postgresql.org/docs/current/warm-standby.html#STREAMING-REPLICATION-SLOTS > > " Replication slots provide an automated way to ensure that the primary > does not remove WAL segments until they have been received by all > standbys, and that the primary does not remove rows which could cause a > recovery conflict > even when the standby is disconnected." > > I'm reading that as: "if there is a replication slot, if the standby is > disconnected, WAL is kept" > > And if we know WAL is kept in the "pg_wal" directory, that sounds like > it could slowly but surely fill up disk space. > > > But again, I'll give them a read. I've read all of logical replication > already, and I feel like I didn't get my answer there. It would be a good idea to provide an a fairly specific outline of what you are trying to achieve, then it would be easier for folks to offer suggestions on what to do or not to do. > > Thanks for the help > > > Regards, > Koen De Groote -- Adrian Klaver adrian.klaver@aklaver.com