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 1ogaoI-0001dG-8B for pgsql-hackers@arkaria.postgresql.org; Fri, 07 Oct 2022 00:01:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ogaoG-0006gj-Ph for pgsql-hackers@arkaria.postgresql.org; Fri, 07 Oct 2022 00:01:48 +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 1ogaoG-0006gZ-EZ for pgsql-hackers@lists.postgresql.org; Fri, 07 Oct 2022 00:01:48 +0000 Received: from mail-lf1-x12a.google.com ([2a00:1450:4864:20::12a]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1ogaoE-0007ch-7b for pgsql-hackers@lists.postgresql.org; Fri, 07 Oct 2022 00:01:48 +0000 Received: by mail-lf1-x12a.google.com with SMTP id bu25so5036443lfb.3 for ; Thu, 06 Oct 2022 17:01:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=MP0e2RSqNhFAH2zc6K/cq7Zo6FFvKLH2PxWPosrAOjc=; b=pn/l6cGjUGN517d/1vevTUClLaf+LOiv3IvsDUtjdPRc83w4HJ2DHEWc8mKQoDFgj2 /57jF8U8NXSn+zvPuRIZ6qT5l2l1el0nhoJkr2vQl8oWxpEmMawk280DHufAzFR6oRi5 fJcfXjhxa5sGdFCtxHtlVTpcF7w6CgqaeUESbbSf444QjabgH7o0Y+Ns7DOpKSiB+sBt A8ZsweuqfAUjK1TEUA23bB8JxCO0Lvjo54c6/4igRZcJ/RE+PAqjRoVqv0ymevpkju3E 2zr+u/aYP48bahgWZdysoCryNgD29lqRG3qZTJ8BX+T6D0mprDMpwCAZ8aKO472Ve3Sw I4+A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=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=MP0e2RSqNhFAH2zc6K/cq7Zo6FFvKLH2PxWPosrAOjc=; b=rK8V4hgBMg1OsG9Ep7sOiH9GyIps8OMbQ219i2EW0us6vZbHalo3d32ztwKPqIUnbT lowgCwdHEhweDsRzvdFx7HXtvAHxHJLelVZjH0y196Zh4/xsMosKV/8W0qSV/J3jhCC4 XX67LB4Pcyd97xD6JbrlqiX3LS5srBkDkoreK2K4Voy1LTkJDuO4sLy4AcS8OGbUAdt9 NeZZ+6/0lQm7u99piFWr+52MyLEw1+Vwk4Syl92Bm+VF2FHJUeRNzzXhEdoxq9mtVWT9 LXsECoTaap0GqY/UzndJyN7I2SeRnK1o2Ix7BGYxvUkN2DdL4OaL88wrX8QWRI2Cm+8V ajtA== X-Gm-Message-State: ACrzQf2tT1IeckZA4SKhPuT4eFmLxFoacZ4DgOVuxVskhJTJYGoWJ3nq BAZngHjtRUamKGUc0ocI96mpzv7l+ZwdP2lljW8= X-Google-Smtp-Source: AMsMyM51z6wYTqEurnFI/ao9kOVRuvfIss8JmvaWMShp2Byq5uZfkBeB6EbT2oT4jVKddJQ5lp4HBgA/n9bKEi98UFE= X-Received: by 2002:ac2:4421:0:b0:4a2:27d2:9649 with SMTP id w1-20020ac24421000000b004a227d29649mr827979lfl.581.1665100904047; Thu, 06 Oct 2022 17:01:44 -0700 (PDT) MIME-Version: 1.0 References: <20221006171601.6um4ey5idm4h62vf@alvherre.pgsql> In-Reply-To: From: Ajin Cherian Date: Fri, 7 Oct 2022 11:01:31 +1100 Message-ID: Subject: Re: Support logical replication of DDLs To: Zheng Li Cc: Alvaro Herrera , vignesh C , "houzj.fnst@fujitsu.com" , Peter Smith , Amit Kapila , Masahiko Sawada , Japin Li , Dilip Kumar , rajesh singarapu , PostgreSQL Hackers Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, Oct 7, 2022 at 8:30 AM Zheng Li wrote: > > > > Some tweaking is made in deparse_drop_command in order to make DROP > > > TRANSFORM deparsing work. This is because the objidentity captured in > > > currentEventTriggerState->SQLDropList contains the keyword 'on', for > > > example "for typename on language lang", but the keyword 'on' is not > > > needed in the current DROP TRANSFORM syntax. So we need to remove the > > > 'on' keyword in objidentity. I'm not sure if this is the best way to > > > handle it, maybe we can consider directly modifying what's captured in > > > currentEventTriggerState->SQLDropList > > > so we don't have the "on" keyword to begin with? > > > > The exact output format for identity is not set in stone; we should only > > set it in stone once we have an actual working case for them. This is > > the first such use, so it seems OK to make minor modifications (such as > > removing an undesirable ON) if it's a reasonable change and allows > > consumer code to be more easily written. > > > So, +1 to dropping ON here. However, if there are further strings that > > need to be modified, let's see what they are. > > Thanks for confirming. Attaching the new patch set that removes the > undesirable ON from getObjectIdentityParts() for TRANSFORM. > Thanks for the new patch-set. Could you add the changes to patch 1 and patch 2, rather than adding a new patch? Otherwise, we'll have a separate patch for each command and it will take double work to keep it updated for each new command added. thanks, Ajin Cherian Fujitsu Australia