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.96) (envelope-from ) id 1vs0LO-00HZ8h-33 for pgsql-hackers@arkaria.postgresql.org; Mon, 16 Feb 2026 15:17:02 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vs0LN-0038mj-1E for pgsql-hackers@arkaria.postgresql.org; Mon, 16 Feb 2026 15:17:01 +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.96) (envelope-from ) id 1vs0LN-0038ma-01 for pgsql-hackers@lists.postgresql.org; Mon, 16 Feb 2026 15:17:01 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1vs0LK-000000012Oz-3yy1 for pgsql-hackers@lists.postgresql.org; Mon, 16 Feb 2026 15:17:00 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2026010100; h=In-Reply-To:Content-Transfer-Encoding:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-ID:Content-Description; bh=t1nmVyW73MAKSGZtkGTPHpusbWe4fy0bk8iCUPJNAz4=; b=YZdLyhFwo831XNiY446UfTNhwo H8XEFW9mTafNbSzEGVf4Azh1y8+HfAba3hV6/M50kTvpk3NKdtlIUPQIAkmv/E2vFWzfa7DKKDemT Tgu+bLhwUWqr2W8im6SZJuMzU8ml1t+KZQFZYk8cbVw5peVtO0C5SVsyBHPmG3DOXPVpQ3mqHZ6na egvl2SPGvYTXqo5M2h+kKUWbpfcIPEDQwrQ9EZfBgVx0iNOOToBsrKDzo0+1f26LkKYqealxs91oJ dTejQM17APEVTGmA+z6cQWqzGcBzoAZQkNEm2ik6ApwUSvoP3dVTlsN87XjrFf4xY8xU0ATr+VZQM Xn/cpq2g==; Received: from bruce by momjian.us with local (Exim 4.98.2) (envelope-from ) id 1vs0LI-00000007hGW-1YnY; Mon, 16 Feb 2026 10:16:56 -0500 Date: Mon, 16 Feb 2026 10:16:56 -0500 From: Bruce Momjian To: Amit Kapila Cc: Masahiko Sawada , Vitaly Davydov , pgsql-hackers@lists.postgresql.org Subject: Re: Support logical replication of DDLs Message-ID: References: <080f9394-c127-4cef-865e-10f2f997125c@postgrespro.ru> 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 Mon, Feb 16, 2026 at 03:24:16PM +0530, Amit Kapila wrote: > On Fri, Feb 13, 2026 at 3:42 AM Bruce Momjian wrote: > > pg_upgrade had a similar challenge, and I found that pushing as much of > > the changes _out_ of pg_upgrade and to other parts of the system, e.g,, > > pg_dump, was a big help. I am not sure if that is possible for > > replicated DDL, but if it is, I would pursue it. > > > > The other reason to pursue a deparsing approach is to allow "Schema > and Object Redirection" between source and target. For example, users > may want to redirect operations from a source object (e.g., > HR.ACCOUNTS on the source) to a different target object (e.g., > HR_BACKUP.ACCT on the target). Many people in the past supported such > flexibility in DDL replication which is one of the reasons we pursued > a deparsing approach in the past though that project/approach is > paused for the time being. I admit that there were many unresolved > challenges apart from the maintenance part of that approach. I understand the desire to get two features from one set of changes, but taking one hard feature and trying to get a second one accomplished usually, for me, ends in failure. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.