On 2021-Jul-14, Dilip Kumar wrote: > I think for insert we are only allowing those rows to replicate which > are matching filter conditions, so if we updating any row then also we > should maintain that sanity right? That means at least on the NEW rows > we should apply the filter, IMHO. Said that, now if there is any row > inserted which were satisfying the filter and replicated, if we update > it with the new value which is not satisfying the filter then it will > not be replicated, I think that makes sense because if an insert is > not sending any row to a replica which is not satisfying the filter > then why update has to do that, right?
Right, that's a good aspect to think about. I think the guiding principle for which tuple to use for the filter is what is most useful to the potential user of the feature, rather than what is the easiest to implement. -- Álvaro Herrera Valdivia, Chile — https://www.EnterpriseDB.com/ "La libertad es como el dinero; el que no la sabe emplear la pierde" (Álvarez)
