On Mon, Nov 29, 2021 at 11:52 PM Jeff Davis <pg...@j-davis.com> wrote: > > On Mon, 2021-11-29 at 08:26 -0800, Mark Dilger wrote: > > > > I agree that if we want to do all of this then that would require a > > > lot of changes. However, giving an error for RLS-enabled tables > > > might > > > also be too restrictive. The few alternatives could be that (a) we > > > allow subscription owners to be either have "bypassrls" attribute > > > or > > > they could be superusers. (b) don't allow initial table_sync for > > > rls > > > enabled tables. (c) evaluate/analyze what is required to allow Copy > > > From to start respecting RLS policies. (d) reject replicating any > > > changes to tables that have RLS enabled. > > Maybe a combination? > > Allow subscriptions with copy_data=true iff the subscription owner is > bypassrls or superuser. And then enforce RLS+WCO during > insert/update/delete. >
Yeah, that sounds reasonable to me. > I don't think it's a big change (correct me if I'm wrong), > Yeah, I also don't think it should be a big change. -- With Regards, Amit Kapila.
