RE: BUG #18644: ALTER PUBLICATION ... SET (publish_via_partition_root) wrong/undocumented behavior.
Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>
From: "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>
To: 'Maxim Boguk' <maxim.boguk@gmail.com>
Cc: vignesh C <vignesh21@gmail.com>, "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>, Amit Kapila <amit.kapila16@gmail.com>
Date: 2024-10-23T10:12:43Z
Lists: pgsql-bugs
Dear Maxim, > Problem also happens if publication is created via FOR ALL TABLES / > FOR TABLES IN SCHEMA (without directly including partition head into > publication). Thanks for pointing out. I also confirmed this issue can happen for FOR ALL TABLES/FOR TABLES IN SCHEMA publications. I modified a documentation. > 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? Just to confirm - you meant like below definitions, right? ``` create table tab (a int) partition by range (a); create table tab_1 partition of tab for values from (-10) to (0); create table tab_2 partition of tab for values from (0) to (10); create publication pub for table tab_1, tab_2 with (publish_via_partition_root = true); ``` For now, changes are replicated as leaf table's one in above case. And I think it is the expected behavior because users expressly specifies them. Best regards, Hayato Kuroda FUJITSU LIMITED
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