| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: bogus: logical replication rows/cols combinations |
| Date: | 2022-05-04 13:56:13 |
| Message-ID: | 6cb47e40-14d4-d29b-d45c-d62f20c091e8@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-05-04 14:00:18 | Re: Add a new function and a document page to get/show all the server hooks |
| Previous Message | Peter Eisentraut | 2022-05-04 13:53:27 | Re: [PATCH] Log details for client certificate failures |