Re: BUG #18644: ALTER PUBLICATION ... SET (publish_via_partition_root) wrong/undocumented behavior.
От | Maxim Boguk |
---|---|
Тема | Re: BUG #18644: ALTER PUBLICATION ... SET (publish_via_partition_root) wrong/undocumented behavior. |
Дата | |
Msg-id | CAK-MWwR-sPHen95jYigWOgA3Zung0-1XAEtoUO5t+Bk6FXe89A@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: BUG #18644: ALTER PUBLICATION ... SET (publish_via_partition_root) wrong/undocumented behavior. (Amit Kapila <amit.kapila16@gmail.com>) |
Ответы |
RE: BUG #18644: ALTER PUBLICATION ... SET (publish_via_partition_root) wrong/undocumented behavior.
|
Список | pgsql-bugs |
> + <para> > + To prevent the issue, you can avoid modifying the partitioned table > + between the <command>ALTER PUBLICATION ... SET</command> and > > Can't the problem happen when any of the leaf tables are modified? If > so, that is not clear from the above statement. Problem also happens if publication is created via FOR ALL TABLES / FOR TABLES IN SCHEMA (without directly including partition head into publication). I have a suspicion that including partition head (directly or via FOR ALL TABLES) into the initial publication - really required to get a problem. What is expected behavior in case when only partitions are included into publication/subscription set, but partition head isn't included and publish_via_partition_root='true' executed? -- Maxim Boguk Senior Postgresql DBA Phone UA: +380 99 143 0000 Phone AU: +61 45 218 5678
В списке pgsql-bugs по дате отправления: