On Tue, Nov 30, 2021 at 3:55 PM Amit Kapila <amit.kapil...@gmail.com> wrote: > > > > > > We can try that way but I think we should still be able to combine in > > > many cases like where all the operations are specified for > > > publications having the table or maybe pubactions are same. So, we > > > should not give up on those cases. We can do this new logic only when > > > we find that pubactions are different and probably store them as > > > independent expressions and corresponding pubactions for it at the > > > current location in the v42* patch (in pgoutput_row_filter). It is > > > okay to combine them at a later stage during execution when we can't > > > do it at the time of forming cache entry. > > > > What about the initial table sync? during that, we are going to > > combine all the filters or we are going to apply only the insert > > filters? > > > > AFAIK, currently, initial table sync doesn't respect publication > actions so it should combine all the filters. What do you think?
Yeah, I have the same opinion. -- Regards, Dilip Kumar EnterpriseDB: http://www.enterprisedb.com
