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 1ogUTj-0006fi-9y for pgsql-hackers@arkaria.postgresql.org; Thu, 06 Oct 2022 17:16:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ogUTh-0001zS-6y for pgsql-hackers@arkaria.postgresql.org; Thu, 06 Oct 2022 17:16:09 +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 1ogUTg-0001zE-U8 for pgsql-hackers@lists.postgresql.org; Thu, 06 Oct 2022 17:16:08 +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 1ogUTd-0004VT-E8 for pgsql-hackers@lists.postgresql.org; Thu, 06 Oct 2022 17:16:07 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id E100B5C0144; Thu, 6 Oct 2022 13:16:04 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Thu, 06 Oct 2022 13:16:04 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:reply-to:sender :subject:subject:to:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; t=1665076564; x=1665162964; bh=y /GwOxmV9HsAFLD10LHMmcfsp5K+n51kKRU8M4ODU2w=; b=OUpUXeZe6tNAM+2vl nOYOk6MV0bZAwdSHqFR29k2tTZY5PzTkY1fgNFeMbjS2qgXSmg17u88qN57teHsS UiGu+i222jwn9/qMTyRgzOsrksHzx5Of80B3roGzzjop9TFsNRyctWNvQQETrlEz ys2k3yzSLLIDXSUNWI8k078HzrQINX6Xi+xQLEoy8kUF/q7bEJLjio+OBNwMl7sM /DOOVsyq4hGV47ODpgXd/UxEsVwyMMvaGPBwTmjRo/laCeaeB+S6hTCigS9VWfvP qg/3NgmnZ0I7nqTdzeE6UixOEilM7+gUaF3IsKALBOsO8cQt2n9sbhBTGj3HwRq8 /sd2w== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrfeeihedgudduudcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpeffhffvvefukfggtggugfgjsehtkeertddttdejnecuhfhrohhmpeetlhhv rghrohcujfgvrhhrvghrrgcuoegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorh hgqeenucggtffrrghtthgvrhhnpedvkedtffduffdtffffheffhfejjefhgfeiueeukeej keffgfdufffhudffffeuveenucffohhmrghinhepvghnthgvrhhprhhishgvuggsrdgtoh hmnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprghl vhhhvghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrgh X-ME-Proxy: Feedback-ID: ia2694551:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 6 Oct 2022 13:16:03 -0400 (EDT) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id 6F0B562; Thu, 6 Oct 2022 19:16:01 +0200 (CEST) Date: Thu, 6 Oct 2022 19:16:01 +0200 From: Alvaro Herrera To: Zheng Li Cc: vignesh C , Ajin Cherian , "houzj.fnst@fujitsu.com" , Peter Smith , Amit Kapila , Masahiko Sawada , Japin Li , Dilip Kumar , rajesh singarapu , PostgreSQL Hackers Subject: Re: Support logical replication of DDLs Message-ID: <20221006171601.6um4ey5idm4h62vf@alvherre.pgsql> 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 On 2022-Oct-06, 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. -- Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/ It does it in a really, really complicated way why does it need to be complicated? Because it's MakeMaker.