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 | CALj2ACXeabk0Eu+t6KKBtsoND3s7q+Njv3cSExD5LyH2GyfmrQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Logical Replication - behavior of ALTER PUBLICATION .. DROP TABLE and ALTER SUBSCRIPTION .. REFRESH PUBLICATION (Amit Kapila <amit.kapila16@gmail.com>) |
Ответы |
Re: Logical Replication - behavior of ALTER PUBLICATION .. DROP TABLE and ALTER SUBSCRIPTION .. REFRESH PUBLICATION
|
Список | pgsql-hackers |
On Sat, Jan 16, 2021 at 12:02 PM Amit Kapila <amit.kapila16@gmail.com> wrote: > > On Sat, Jan 16, 2021 at 11:52 AM Bharath Rupireddy > <bharath.rupireddyforpostgres@gmail.com> wrote: > > > > I made an entry in the commitfest[1], so that the patches will get a > > chance to run on all the platforms. > > > > Attaching v4 patch set i.e. 0001 - fix, 0002 - test case. > > > > In the test, can we have multiple publications for the subscription > because that is how we discovered that the originally proposed patch > was not correct? Also, is it possible to extend some of the existing > tests in 001_rep_changes.pl or anywhere so that we can avoid some cost > of the replication setup. Sure, I will add the multiple publications use case provided by japin and also see if I can move the tests from 100_bugs.pl to 0001_rep_changes.pl. With Regards, Bharath Rupireddy. EnterpriseDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: