Re: Added schema level support for publication.
От | Greg Nancarrow |
---|---|
Тема | Re: Added schema level support for publication. |
Дата | |
Msg-id | CAJcOf-c=y2NsfOp5cT4q_TEKgtroOBK_pAEyurhSHQC8PCpKgA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Added schema level support for publication. (vignesh C <vignesh21@gmail.com>) |
Ответы |
Re: Added schema level support for publication.
|
Список | pgsql-hackers |
On Fri, Aug 27, 2021 at 4:13 PM vignesh C <vignesh21@gmail.com> wrote: > > I have implemented this in the 0003 patch, I have kept it separate to > reduce the testing effort and also it will be easier if someone > disagrees with the syntax. I will merge it to the main patch later > based on the feedback. Attached v22 patch has the changes for the > same. I notice that "CREATE PUBLICATION pub1 FOR ALL TABLES IN SCHEMA sc1, TABLE sc1.test;" maintains the table separately and results in the following in the \dRp+ output: Tables: "sc1.test" Schemas: "sc1" and also then "ALTER PUBLICATION pub1 DROP ALL TABLES IN SCHEMA sc1;" still leaves the "sc1.test" table in the publication. Is there a reason why we don't/can't support "ALTER SUBSCRIPTION ... SET ALL TABLES;"? (I know it wasn't supported before, but now "ALTER SUBSCRIPTION ... SET ALL TABLES IN SCHEMA ..." is being supported) I notice that the v22-0003 documentation updates for ALTER SUBSCRIPTION are missing - but you're probably waiting on all feedback before proceeding with that. Regards, Greg Nancarrow Fujitsu Australia
В списке pgsql-hackers по дате отправления: