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 1rPKNb-00Aoqp-A8 for pgsql-hackers@arkaria.postgresql.org; Mon, 15 Jan 2024 10:39:43 +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 1rPKNa-00Ez6y-Am for pgsql-hackers@arkaria.postgresql.org; Mon, 15 Jan 2024 10:39:42 +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 1rPKNa-00Ez6q-16 for pgsql-hackers@lists.postgresql.org; Mon, 15 Jan 2024 10:39:42 +0000 Received: from mail-oa1-x2b.google.com ([2001:4860:4864:20::2b]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rPKNX-001uxQ-RZ for pgsql-hackers@postgresql.org; Mon, 15 Jan 2024 10:39:41 +0000 Received: by mail-oa1-x2b.google.com with SMTP id 586e51a60fabf-2044ecf7035so5892681fac.0 for ; Mon, 15 Jan 2024 02:39:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1705315177; x=1705919977; darn=postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=5WH1URUPNnuL90FyPCkvKACmJtvATyUBeXq6IgwgBaE=; b=DB8Sc9YiVIt1MtRrS9FSUuRNmmMus14St11IIwukVG1iFi62rUJ03j6fLyh5czu6pZ VSYvTyfoqM70PSF4eujZoeloc4kWlboM4ftQcpxKfkqPIP/etThMlHZNyhblQMnF0Z+X uF2zGsvvdl9wr4VrDF/y+tamWR2PYDoLoOJw8s6iqwxUqMFSkGI/T7KrGD5oY0jg0Ius jn3sQv1V5Vq5Dq5X/TLFT5RcMxhMNNjcysZtftT6734+M7XjZDKUY+cQnRChnYovJWgn JlOnXqKuPwbcayW8FwAJs0jKIGjs4QElEiIWE3zMU2bckE5tIm19IzmjlgoUaXZCbvWT zXsA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1705315177; x=1705919977; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=5WH1URUPNnuL90FyPCkvKACmJtvATyUBeXq6IgwgBaE=; b=ZuEXN9EqTkpYQDHyt4478+HloicTEMNQyi9tRw83aPSbIUT/Uwz37AKdvO0QK3wTOD t/Hkz/mparoFzeTPNnfQJcftEuOeIkCbcoe07vEhHe0NKw1eWAQIzyQ6Pms+N6tMzfso pEBHEEzNlr1YLzuyLJnePBzgmYtAF+vidw7SQF8Wrj4Xv33NaNPPJk97CvULzz5TIbAd 3gnhu4pNCNl36Udmgqb2HQaEEfMzbq0ufJ58goBCApFF2emfQhGVKNj2RO2ndmNzWs8d 8nGbcH7vz4o9w/lqGtq2151E7EPxQ7M74+r5w4tD5ObdGVmXbDqcGBBFiHY+UAalgZYO VWSg== X-Gm-Message-State: AOJu0Yzz5gjM1M4eShBEXuPIJpcCaTk1CefT6q3XOU35k+mkpEVfVoG+ J9lTIddZgONI7R3EwNmBSb9rQXLYTRt2n5nZq4k= X-Google-Smtp-Source: AGHT+IGxBRifVwn+e7G4jVsW4iwtdwWtUzSkHJ3oehJ6WBnXSIdZ8Nbh7abGHd3HdQvToO3QgC+A+PvVbaw5rwPP0rY= X-Received: by 2002:a05:6870:9a22:b0:206:90:7cda with SMTP id fo34-20020a0568709a2200b0020600907cdamr7853066oab.106.1705315177262; Mon, 15 Jan 2024 02:39:37 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Amit Kapila Date: Mon, 15 Jan 2024 16:09:26 +0530 Message-ID: Subject: Re: Synchronizing slots from primary to standby To: Bertrand Drouvot 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 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, Jan 15, 2024 at 2:54=E2=80=AFPM Bertrand Drouvot wrote: > > On Sat, Jan 13, 2024 at 10:05:52AM +0530, Amit Kapila wrote: > > On Fri, Jan 12, 2024 at 12:07=E2=80=AFPM Bertrand Drouvot > > wrote: > > > Maybe the "best" approach would be to have a way to detect that a slo= t 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 d= o 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 oth= er side > that would also probably simplify (and less bug prone in the mid-long ter= m?) > other parts of the code. > After following Sawada-San's suggestion to not copy the 'failover' option there doesn't seem to be much special handling, so there is probably less to simplify. --=20 With Regards, Amit Kapila.