Re: BUG #18644: ALTER PUBLICATION ... SET (publish_via_partition_root) wrong/undocumented behavior.
От | Amit Kapila |
---|---|
Тема | Re: BUG #18644: ALTER PUBLICATION ... SET (publish_via_partition_root) wrong/undocumented behavior. |
Дата | |
Msg-id | CAA4eK1LNuj1CRY1Mb1W0XkbB6pL6PNXrJcg+Ww5QdvKGm6Mm3w@mail.gmail.com обсуждение исходный текст |
Ответ на | BUG #18644: ALTER PUBLICATION ... SET (publish_via_partition_root) wrong/undocumented behavior. (PG Bug reporting form <noreply@postgresql.org>) |
Ответы |
Re: BUG #18644: ALTER PUBLICATION ... SET (publish_via_partition_root) wrong/undocumented behavior.
|
Список | pgsql-bugs |
On Wed, Oct 9, 2024 at 6:04 PM Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com> wrote: > > Thanks for giving comments! Since I'm not a native I followed your points. > I ran Grammaly just in case and it said OK. > > PSA new version. > + <caution> + <para> + When the partition root table is specified as the replication target + instead of its leaf tables, altering the + <literal>publish_via_partition_root</literal> parameter during + replication can cause data loss or duplication. This happens because + the subscriber initially subscribed to the leaf tables. This assumes that the user is always changing publish_via_partition_root from 'false' to 'true'. Can't she change from 'false' to 'true' as well? + <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. -- With Regards, Amit Kapila.
В списке pgsql-bugs по дате отправления: