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 1rPJCz-00Agnq-Nv for pgsql-hackers@arkaria.postgresql.org; Mon, 15 Jan 2024 09:24:42 +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 1rPJCy-00ERfH-1C for pgsql-hackers@arkaria.postgresql.org; Mon, 15 Jan 2024 09:24:40 +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.94.2) (envelope-from ) id 1rPJCx-00ERf9-O3 for pgsql-hackers@lists.postgresql.org; Mon, 15 Jan 2024 09:24:39 +0000 Received: from mail-wm1-x32a.google.com ([2a00:1450:4864:20::32a]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rPJCv-001cs1-Ao for pgsql-hackers@postgresql.org; Mon, 15 Jan 2024 09:24:38 +0000 Received: by mail-wm1-x32a.google.com with SMTP id 5b1f17b1804b1-40e76109cdeso9598205e9.0 for ; Mon, 15 Jan 2024 01:24:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1705310676; x=1705915476; darn=postgresql.org; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date:from:to :cc:subject:date:message-id:reply-to; bh=fDqBK0i7jVO6YNk7nofV78x5tpTKbP5NJalV+SrMyHM=; b=YSTxPCJ6HmzC3+17oGpdd8rd405je4SCX6joGSev/moAmxnKjrKI0V23tBpp82wfK9 +poF72z/aVHg6jMk77Wd49XFpCdRp2Kr5rWUJTAyS+8NtaOp/RKH6qMGD/r/oXtIyc4j rhwaWrHrpAKSl5I3z7Xjc+nVzxW7HLi/HiTZ7aBZJXScAEuXD3cHpXqp5pl8Z4Ja5tzD 9lbOt+4Z80ywGSXKso3UN2bF7oZa+SWSUks3lNb42ntzWIuti9DbjGYAK9Kh+YgaOi55 oWneXnI59vRDMEYVjYWrjAtf/DGjOGQA/g+VWFwnNRi/2MjCWmKZRaZIyaqzvC+bhN+h HtTA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1705310676; x=1705915476; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=fDqBK0i7jVO6YNk7nofV78x5tpTKbP5NJalV+SrMyHM=; b=TKec8UOqCxDFRQ6JclY3DcOJz4g4j+9jnx0zSjSqRf+ZyJZCFGoMQv50pAyWi3lWft FWwupavKHGuyU+P+Sf9p9SfJJJNf2cQ/PWz+DFpEoilPu2N9FdcyBXrJvRDNnh1JcukT vu1Y/wgqg8X35QRNQfS3R8PZKbRziIjtZwjYVU3rYGHqOE00Ejq64gm3qU9o25ogGj/3 6RqkCr5+rVGAvTkQjCZ6FBikVvHBOWxleTrbUj294PRgrPPQ+/OIwQmXcWIUD9EAO7ex 3Ob4evKp920xrTvf+cIicnQ9DRsARqoflgicZboZFDNOEkKxVHhr5EiY1HNxzw9ERl8/ cSsA== X-Gm-Message-State: AOJu0YyE99Kt3qRFkuy7sOKIpDDghLhe7yZ54sDc+pha3U76Vk66LrUV 6xcHSbl8d954icOvPKo0OrM= X-Google-Smtp-Source: AGHT+IEg6Jni03qJQasYAytukATfA7JfK49OGYJZrQRxNb6YgUayhFO57bc5mCzT2wm884xsalUhyg== X-Received: by 2002:a05:600c:1390:b0:40e:4693:93f7 with SMTP id u16-20020a05600c139000b0040e469393f7mr2510510wmf.32.1705310675487; Mon, 15 Jan 2024 01:24:35 -0800 (PST) Received: from ip-10-97-1-34.eu-west-3.compute.internal (ec2-15-236-134-5.eu-west-3.compute.amazonaws.com. [15.236.134.5]) by smtp.gmail.com with ESMTPSA id i17-20020a05600c355100b0040d5f466deesm15111237wmq.38.2024.01.15.01.24.34 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 15 Jan 2024 01:24:35 -0800 (PST) Date: Mon, 15 Jan 2024 09:24:33 +0000 From: Bertrand Drouvot To: Amit Kapila Cc: "Zhijie Hou (Fujitsu)" , Masahiko Sawada , Dilip Kumar , shveta malik , Peter Smith , Nisha Moond , "Hayato Kuroda (Fujitsu)" , Bharath Rupireddy , Peter Eisentraut , Bruce Momjian , Ashutosh Sharma , Andres Freund , pgsql-hackers , Ajin Cherian , Alvaro Herrera Subject: Re: Synchronizing slots from primary to standby Message-ID: References: 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 Hi, On Sat, Jan 13, 2024 at 10:05:52AM +0530, Amit Kapila wrote: > On Fri, Jan 12, 2024 at 12:07 PM Bertrand Drouvot > wrote: > > Maybe the "best" approach would be to have a way to detect that a slot has been > > re-created on the primary (but that would mean rely on more than the slot name > > to "identify" a slot and probably add a new member to the struct to do so). > > > > Right, I also thought so but not sure further complicating the slot > machinery is worth detecting this case explicitly. If we see any > problem with the idea discussed then we may need to think something > along those lines. Yeah, let's see. On one side that would require extra work but on the other side that would also probably simplify (and less bug prone in the mid-long term?) other parts of the code. Regards, -- Bertrand Drouvot PostgreSQL Contributors Team RDS Open Source Databases Amazon Web Services: https://aws.amazon.com