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: Maxim Boguk <maxim.boguk@gmail.com>, vignesh C <vignesh21@gmail.com>, "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Date: 2024-10-24T08:46:35Z
Lists: pgsql-bugs
On Wed, Oct 23, 2024 at 3:42 PM Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com> wrote: > > > 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. > I don't think we need to mention this in docs, the following change: "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." added by you appears odd to me. -- 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