Re: Logical Replication - behavior of ALTER PUBLICATION .. DROP TABLE and ALTER SUBSCRIPTION .. REFRESH PUBLICATION
От | Bharath Rupireddy |
---|---|
Тема | Re: Logical Replication - behavior of ALTER PUBLICATION .. DROP TABLE and ALTER SUBSCRIPTION .. REFRESH PUBLICATION |
Дата | |
Msg-id | CALj2ACUYSswj3Cy9rm6GrK68xtAF9vewonkmwso7QmE5gNUJdA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Logical Replication - behavior of ALTER PUBLICATION .. DROP TABLE and ALTER SUBSCRIPTION .. REFRESH PUBLICATION (Li Japin <japinli@hotmail.com>) |
Ответы |
Re: Logical Replication - behavior of ALTER PUBLICATION .. DROP TABLE and ALTER SUBSCRIPTION .. REFRESH PUBLICATION
|
Список | pgsql-hackers |
On Tue, Jan 12, 2021 at 4:47 PM Li Japin <japinli@hotmail.com> wrote: > IIUC the logical replication only replicate the tables in publication, I think > when the tables that aren't in publication should not be replicated. > > Attached the patch that fixes it. Thought? With that change, we don't get the behaviour that's stated in the document - "The ADD TABLE and DROP TABLE clauses will add and remove one or more tables from the publication. Note that adding tables to a publication that is already subscribed to will require a ALTER SUBSCRIPTION ... REFRESH PUBLICATION action on the subscribing side in order to become effective" - https://www.postgresql.org/docs/devel/sql-alterpublication.html. The publisher stops sending the tuples whenever the relation gets dropped from the publication, not waiting until alter subscription ... refresh publication on the subscriber. With Regards, Bharath Rupireddy. EnterpriseDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: