Message-ID: <6cb47e40-14d4-d29b-d45c-d62f20c091e8@enterprisedb.com>
Date: Wed, 4 May 2022 15:56:13 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0)
 Gecko/20100101 Thunderbird/91.8.1
Subject: Re: bogus: logical replication rows/cols combinations
Content-Language: en-US
To: Tomas Vondra <tomas.vondra@enterprisedb.com>,
 Amit Kapila <amit.kapila16@gmail.com>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>,
 Pg Hackers <pgsql-hackers@lists.postgresql.org>
References: <006d5ffc-1e7a-5cf2-c507-88eee6e0c14d@enterprisedb.com>
 <202204270943.4ol7indtwv3i@alvherre.pgsql>
 <CAA4eK1+9LCX3qKyo9S4uaaciM0WqZrP6m=kMzufgpuv=a=PgXQ@mail.gmail.com>
 <39077967-c327-eddb-ac4b-7d64117944fb@enterprisedb.com>
 <CAA4eK1K+PkkC6_FDemGMC_i+Aakx+3=QG-g4We3BdCK7dK_bgA@mail.gmail.com>
 <338e719c-4bc8-f40a-f701-e29543a264e4@enterprisedb.com>
 <47dd2cb9-4e96-169f-15ac-f9407fb54d43@enterprisedb.com>
 <a7a5e79f-053a-cff8-6b2c-f7ac4bab9920@enterprisedb.com>
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
In-Reply-To: <a7a5e79f-053a-cff8-6b2c-f7ac4bab9920@enterprisedb.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/6cb47e40-14d4-d29b-d45c-d62f20c091e8%40enterprisedb.com>
Precedence: bulk


On 03.05.22 21:40, Tomas Vondra wrote:
> So what's wrong with merging the column lists as implemented in the v2
> patch, posted a couple days ago?

Merging the column lists is ok if all other publication attributes 
match.  Otherwise, I think not.

> I don't think triggers are a suitable alternative, as it executes on the
> subscriber node. So you have to first copy the data to the remote node,
> where it gets filtered. With column filters the data gets redacted on
> the publisher.

Right, triggers are not currently a solution.  But you could imagine a 
redaction filter system that runs on the publisher that modifies rows 
before they are sent out.