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 1pSMMK-0006ID-GF for pgsql-hackers@arkaria.postgresql.org; Wed, 15 Feb 2023 18:18:24 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pSMMJ-0002Dk-BQ for pgsql-hackers@arkaria.postgresql.org; Wed, 15 Feb 2023 18:18:23 +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 1pSMMJ-0002Db-1t for pgsql-hackers@lists.postgresql.org; Wed, 15 Feb 2023 18:18:23 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pSMMG-0005Ci-Pw for pgsql-hackers@postgresql.org; Wed, 15 Feb 2023 18:18:22 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 13E2C5C0200; Wed, 15 Feb 2023 13:18:20 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Wed, 15 Feb 2023 13:18:20 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=anarazel.de; h= cc:cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm1; t=1676485100; x=1676571500; bh=u6unQUu2St FxG/Esu2jbmN9anZKWpOB3+WCstvuHb3U=; b=na8jWsSTAm/fwT4kyt0UW9fycf n7EgOCV7T51YWj32Cm/IJrf2/l6LoUbYwPRfYLCelK7sBRwIFeZL0Plvrm6LFVbV uFBZXGkKTY+J1EK8vA3iBeVqahUcvQRZUumEUxzxQKXiMVIQsvQh2SZ9rD7N84CK TKmlKtIScjR/7wvWEHO5PA42ybBoXZxsAwtuKFRT0RlFdE0u7rwYKc9HHBRAZlUM jxEKgpCtqbZm2G5nhdvJpGEvT0Fv0SsXRT3hckyEIQX98D6Reh8m+hAqn5oYYmNz 9PfOFK4N0QTbKtmu0Zu06UX/xD1Q6Xn7d4gBAaHPv0Yg7qw3Jl5BUCHokJsA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references: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=1676485100; x=1676571500; bh=u6unQUu2StFxG/Esu2jbmN9anZKW pOB3+WCstvuHb3U=; b=Xi+TylW1bDAWqjEPSrQ/uN4vQCTLdjhX5G1nOb2NcL3n Den0BGjJXma79pMZsnDifG9kfneDwyn65kX8Fnn0iKPxL0nm+idwyLLrr9zpVsv6 FR3BKPp/m7WYmv8XFCw1L+JAjz1PjgOK7WMclDIMeBD6AxL9RWUYhyor+TSnZsOh M+R07IE33kxu9kK4rMw+aXjKXtsLH5NAkYj6hPog8D18qkHswuetiNIlDbVnnoBN UqZNfVHtwi2yBVkKMXGHEuTekXhkgqrsutGGJB6BOQnl/9xBmgnPauaNgz08Um/r N1WpAo4nnWsjcTAkr5xboDbjrmgKAnM2l3HjW6HUwg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudeihedguddtgecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpeffhffvvefukfhfgggtuggjsehttdertddttddvnecuhfhrohhmpeetnhgu rhgvshcuhfhrvghunhguuceorghnughrvghssegrnhgrrhgriigvlhdruggvqeenucggtf frrghtthgvrhhnpedvffefvefhteevffegieetfefhtddvffejvefhueetgeeludehteev udeitedtudenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhroh hmpegrnhgurhgvshesrghnrghrrgiivghlrdguvg X-ME-Proxy: Feedback-ID: id4a34324:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 15 Feb 2023 13:18:19 -0500 (EST) Date: Wed, 15 Feb 2023 10:18:18 -0800 From: Andres Freund To: Ashutosh Sharma Cc: "Drouvot, Bertrand" , Robert Haas , Thomas Munro , Alvaro Herrera , Ibrar Ahmed , Amit Khandekar , fabriziomello@gmail.com, tushar , Rahila Syed , pgsql-hackers Subject: Re: Minimal logical decoding on standbys Message-ID: <20230215181818.mhmwp3pvt3crtalo@awork3.anarazel.de> References: <1f2ad9fd-53ff-74cc-a602-72d45423bcab@gmail.com> <05c0c4f3-82eb-bc6d-c876-5a265c05927b@gmail.com> <20230106034036.2m4qnn7ep7b5ipet@awork3.anarazel.de> <805540ba-b132-30f2-563d-cf9acc527008@gmail.com> <2d62f212-fce6-d639-b9eb-2a5bc4bec3b4@gmail.com> <20230112181630.lpqqty2vzuatgwcl@awork3.anarazel.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, On 2023-02-15 18:02:11 +0530, Ashutosh Sharma wrote: > Thanks Andres. I have one more query (both for you and Bertrand). I > don't know if this has already been answered somewhere in this mail > thread, if yes, please let me know the mail that answers this query. > > Will there be a problem if we mandate the use of physical replication > slots and hot_standby_feedback to support minimum LD on standby. I > know people can do a physical replication setup without a replication > slot or even with hot_standby_feedback turned off, but are we going to > have any issue if we ask them to use a physical replication slot and > turn on hot_standby_feedback for LD on standby. This will reduce the > code changes required to do conflict handling for logical slots on > standby which is being done by v50-0001 and v50-0002* patches > currently. I don't think it would. E.g. while restoring from archives we can't rely on knowing that the slot still exists on the primary. We can't just do corrupt things, including potentially crashing, when the configuration is wrong. We can't ensure that the configuration is accurate all the time. So we need to detect this case. Hence needing to detect conflicts. > IMHO even in normal scenarios i.e. when we are not doing LD on > standby, we should mandate the use of a physical replication slot. I don't think that's going to fly. There plenty scenarios where you e.g. don't want to use a slot, e.g. when you want to limit space use on the primary. Greetings, Andres Freund