Re: Skipping schema changes in publication
От | Amit Kapila |
---|---|
Тема | Re: Skipping schema changes in publication |
Дата | |
Msg-id | CAA4eK1KYQz7cf46_D=6VkZ4J6Y8vJ88MMi=6zm2TJXDP+V1mLg@mail.gmail.com обсуждение исходный текст |
Ответ на | RE: Skipping schema changes in publication ("Zhijie Hou (Fujitsu)" <houzj.fnst@fujitsu.com>) |
Список | pgsql-hackers |
On Wed, Apr 16, 2025 at 8:22 AM Zhijie Hou (Fujitsu) <houzj.fnst@fujitsu.com> wrote: > > On Thu, Apr 10, 2025 at 7:25 PM Amit Kapila wrote: > > > > On Tue, Jan 9, 2024 at 12:02 PM vignesh C <vignesh21@gmail.com> wrote: > > > > > > As I did not see much interest from others, I'm withdrawing this patch > > > for now. But if there is any interest others in future, I would be > > > more than happy to work on this feature. > > > > > > > Just FYI, I noticed a use case for this patch in email [1]. Users would like to > > replicate all except a few columns having sensitive information. The challenge > > with current column list features is that adding new tables to columns would > > lead users to change the respective publications as well. > > > > [1] - > > https://www.postgresql.org/message-id/tencent_DCDF626FCD4A556C51BE > > 270FDC3047540208%40qq.com > > BTW, I noticed that debezium, an open source distributed platform for change > data capture that replies on logical decoding, also support specifying the > column exclusion list[1]. So, this indicates that there could be some use cases > for this feature. > Thanks for sharing the link. I see that they support both the include and exclude lists for columns and tables. -- With Regards, Amit Kapila.
В списке pgsql-hackers по дате отправления: