Re: Feature Recommendations for Logical Subscriptions - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Feature Recommendations for Logical Subscriptions
Date
Msg-id CAA4eK1JQzbY-77JFt0wEazwxG3j=afhHxG1n2_Qx=PzuLKFPrg@mail.gmail.com
Whole thread Raw
In response to Re: Feature Recommendations for Logical Subscriptions  (Peter Smith <smithpb2250@gmail.com>)
Responses Re: Feature Recommendations for Logical Subscriptions
Re: Feature Recommendations for Logical Subscriptions
List pgsql-hackers
On Fri, Apr 11, 2025 at 3:40 AM Peter Smith <smithpb2250@gmail.com> wrote:
>
> FYI, the Column List documentation [1] says
> ------
> However, do not rely on this feature for security: a malicious
> subscriber is able to obtain data from columns that are not
> specifically published. If security is a consideration, protections
> can be applied at the publisher side.
> ------
>
> IIRC, this was something to do with how the COPY done by the initial
> table sync might be manipulated by a malicious subscriber. I think you
> can find more details about this in the original thread when Column
> Lists were introduced. e.g. try searching this [2] thread for the word
> "security".
>

The same thing applies here as well. The only key difference is user
convenience in two ways: (a) when there are a lot of columns, say 100
columns, and user would like to send all data except 2 columns, (b)
adding new columns to table would require users to again run the DDL
to change the column list.

These are primarily the two pain points YeXiu wants us to solve.
YeXiu, if I misunderstood your intention, feel free to add.

--
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Peter Smith
Date:
Subject: Re: Proposal: Filter irrelevant change before reassemble transactions during logical decoding
Next
From: Michael Paquier
Date:
Subject: Re: stats.sql fails during installcheck on mac