Re: BUG #18644: ALTER PUBLICATION ... SET (publish_via_partition_root) wrong/undocumented behavior.
Amit Kapila <amit.kapila16@gmail.com>
From: Amit Kapila <amit.kapila16@gmail.com>
To: "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>
Cc: vignesh C <vignesh21@gmail.com>, Maxim Boguk <maxim.boguk@gmail.com>, "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Date: 2024-10-14T06:25:34Z
Lists: 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.
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Doc: Add a caution in alter publication.
- b8a046081c43 18.0 landed