Re: row filtering for logical replication
От | Amit Kapila |
---|---|
Тема | Re: row filtering for logical replication |
Дата | |
Msg-id | CAA4eK1KGK9WxtRZ19pOivh9V-6ncxNCzDhkLeL7C-5+WgsaDsg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: row filtering for logical replication (Dilip Kumar <dilipbalaut@gmail.com>) |
Ответы |
Re: row filtering for logical replication
Re: row filtering for logical replication |
Список | pgsql-hackers |
On Mon, Jul 19, 2021 at 4:31 PM Dilip Kumar <dilipbalaut@gmail.com> wrote: > > On Mon, Jul 19, 2021 at 3:12 PM Amit Kapila <amit.kapila16@gmail.com> wrote: > > > > Maybe a second option is to have replication change any UPDATE into > > > either an INSERT or a DELETE, if the old or the new row do not pass the > > > filter, respectively. That way, the databases would remain consistent. > > Yeah, I think this is the best way to keep the data consistent. > Today, while studying the behavior of this particular operation in other databases, I found that IBM's InfoSphere Data Replication does exactly this. See [1]. I think there is a merit if want to follow this idea. [1] - https://www.ibm.com/docs/en/idr/11.4.0?topic=rows-search-conditions -- With Regards, Amit Kapila.
В списке pgsql-hackers по дате отправления: