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 1mvn8F-0003sQ-AM for pgsql-hackers@arkaria.postgresql.org; Fri, 10 Dec 2021 21:08:43 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mvn8C-0003MF-17 for pgsql-hackers@arkaria.postgresql.org; Fri, 10 Dec 2021 21:08:40 +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 1mvn8A-0003M5-Tj for pgsql-hackers@lists.postgresql.org; Fri, 10 Dec 2021 21:08:39 +0000 Received: from wout4-smtp.messagingengine.com ([64.147.123.20]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mvn85-00082L-GC for pgsql-hackers@postgresql.org; Fri, 10 Dec 2021 21:08:38 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id AF9E03201F87; Fri, 10 Dec 2021 16:08:28 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 10 Dec 2021 16:08:29 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:subject:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; bh=HZIsb6U+lrcfKVLXlBJyvZMbRXQLpgIpkFV6elXo8Ps=; b=EU8zZC98 pRIU+LMWRh3yTojhSJrTGWzAJjnqkG9OF1H+hhw9YZqVxTeipgYAXfa7g96N8kdb FlLsuO6stMnsW8oULv7baSAewel4aju9XKAqw5kkunejbY4/ul+3CcT7iqgG82ds ofQFCVdpVALCJB75HxWYJI6DUvckFmbU9CUhMGfJbg4Hibcx0m0jupbiCCGyffig xArihB8AYaGjLxr04iKK+QA2HGKgy/zdM8B862cek+qkZAnyWUzavdtvcwTaaQW+ EOqvLPEgOZm2RcgVYfuhmB3x/S3hZQg55+RxRj9W8wi51cQLyNu48tieABr9Zy/a yhIZlgd21MrZkw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrkedvgddugeeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepfffhvffukfggtggugfgjsehtkeertddttdejnecuhfhrohhmpeetlhhvrghr ohcujfgvrhhrvghrrgcuoegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhgqe enucggtffrrghtthgvrhhnpedujeevjeffjeevuddutedvkeeiueeitddvieelfeekveej udefgeeuvdejhfeuleenucffohhmrghinhepvghnthgvrhhprhhishgvuggsrdgtohhmne cuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprghlvhhh vghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrgh X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 10 Dec 2021 16:08:27 -0500 (EST) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id A23072A075D; Fri, 10 Dec 2021 18:08:24 -0300 (-03) Date: Fri, 10 Dec 2021 18:08:24 -0300 From: Alvaro Herrera To: Rahila Syed Cc: Amit Kapila , Tomas Vondra , Peter Smith , PostgreSQL-development Subject: Re: Column Filtering in Logical Replication Message-ID: <202112102108.2yawji3o55hw@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <202112102002.pejiewltbf3c@alvherre.pgsql> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2021-Dec-10, Alvaro Herrera wrote: > I thought about this some more and realized that our earlier conclusions > were wrong or at least inconvenient. I think that the best behavior if > you drop a column from a table is to remove the column from the > publication column list, and do nothing else. > Should be fairly quick to implement ... on it now. Actually it's not so easy to implement. -- Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/ "No hay ausente sin culpa ni presente sin disculpa" (Prov. francés)