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 1plpZV-0007jC-Ox for pgsql-hackers@arkaria.postgresql.org; Mon, 10 Apr 2023 11:20:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1plpZU-0000oG-Fo for pgsql-hackers@arkaria.postgresql.org; Mon, 10 Apr 2023 11:20:28 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1plpZU-0000o6-4m for pgsql-hackers@lists.postgresql.org; Mon, 10 Apr 2023 11:20:28 +0000 Received: from mail-ot1-x334.google.com ([2607:f8b0:4864:20::334]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1plpZO-00216O-V5 for pgsql-hackers@lists.postgresql.org; Mon, 10 Apr 2023 11:20:27 +0000 Received: by mail-ot1-x334.google.com with SMTP id c2-20020a056830348200b006a3ab0ba8a2so6485840otu.1 for ; Mon, 10 Apr 2023 04:20:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1681125621; x=1683717621; 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=/kB6dlA7qe5qbz6CFe3s+SLeicdaCdbyMVUCkXTlp8g=; b=qkzK7CiX8CRapYW4jsjxc5cqkNcGgXi5ESk48U/RQF1zCDrYlGvjTP6fhJ1CbYuQuG 9mWuYrWatctV65t8+o2WtC6qnGUiS9rB/5PP/gJWgfOWhUhAm+lKagJQFC7wsEoKyZ5V /DM+OvQqpto6QIQqPc6lGMj4uLbm/KAWcnTXsawSEOdQDBsLaGY8HFdDIg9Rqln0t1jV 26xgfun+LVSvmCfTDC00xe3HVB3+ls8NqE4H3TqERUk373ZmnmAH2rrECxshb/f6vVV/ ihMBZR79MZSzcqGbEPNhaVlr8P+vWTE/kM5Eb/MxswW38flivB5lkD4hL35fyNhlFmlm 6XvA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1681125621; x=1683717621; 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=/kB6dlA7qe5qbz6CFe3s+SLeicdaCdbyMVUCkXTlp8g=; b=BvFd35OEafVFbsDaX33DXoQxh53VVZfHr10B50DbPt5JnVf/7Dsgui9L/qIiR7Olpy /uxvnqRB/V2DEVn2ABGWtEYhar1enEpkLY+Dq99//7kPNLQITFPUCldjCobSNiCskaP4 nYoru09FX3PF6ApGcTEin1yaGe9fjW2NkrunEB/yucqgvgbOXOi9hzImWaHvcvl0DTAA i0UgLDYRvNCqeh7HTIEqDN0RHsEutT13VOoUFdy9Xj2PXkbT5EasFpEr6CyNg4TfeTcK ZzVw67YlMdwB9IPZ2LJSYUQlBpTsxbaeGG/pRYiYn77OGRSu2NENpd714ZXg3N8+KzwH VSmA== X-Gm-Message-State: AAQBX9f7fKv6nHH2KeqWDYDCalkeylT7Auh7zSDDgbTYGm+rjIVfBEK1 aMvk/eXSguaEhcmZevbp4xhnMaIZKu5LAl993h8nLGN8Fa3ucA== X-Google-Smtp-Source: AKy350Y7CXxYl9JM1t9Nsu8vsOkm4LMzSgHmD6Df/eswjky8s1+MWigehcT7gb4CuheQVsYwKjDLk8ktjBtm6MeOGIY= X-Received: by 2002:a05:6830:614:b0:688:cf52:6e18 with SMTP id w20-20020a056830061400b00688cf526e18mr2478156oti.4.1681125620757; Mon, 10 Apr 2023 04:20:20 -0700 (PDT) MIME-Version: 1.0 References: <3032112.1679865718@sss.pgh.pa.us> In-Reply-To: From: Amit Kapila Date: Mon, 10 Apr 2023 16:50:09 +0530 Message-ID: Subject: Re: Support logical replication of DDLs To: "houzj.fnst@fujitsu.com" Cc: shveta malik , vignesh C , Ajin Cherian , "wangw.fnst@fujitsu.com" , Runqi Tian , Peter Smith , Tom Lane , li jie , Dilip Kumar , Alvaro Herrera , Masahiko Sawada , Japin Li , rajesh singarapu , PostgreSQL Hackers , Zheng Li 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 Fri, Apr 7, 2023 at 8:52=E2=80=AFAM houzj.fnst@fujitsu.com wrote: > > Sorry, there was a miss when rebasing the patch which could cause the > CFbot to fail and here is the correct patch set. > I see the following note in the patch: "Note: For ATTACH/DETACH PARTITION, we haven't added extra logic on the subscriber to handle the case where the table on the publisher is a PARTITIONED TABLE while the target table on the subscriber side is a NORMAL table. We will research this more and improve it later." and wonder what should we do about this. I can think of the following possibilities: (a) Convert a non-partitioned table to a partitioned one and then attach the partition; (b) Add the partition as a separate new table; (c) give an error that table types mismatch. For Detach partition, I don't see much possibility than giving an error that no such partition exists or something like that. Even for the Attach operation, I prefer (c) as the other options don't seem logical to me and may add more complexity to this work. Thoughts? --=20 With Regards, Amit Kapila.