Re: [PATCH] Skip unpublishable child tables when adding parent to publication
Euler Taveira <euler@eulerto.com>
From: "Euler Taveira" <euler@eulerto.com>
To: "Amit Kapila" <amit.kapila16@gmail.com>,
"houzj.fnst@fujitsu.com" <houzj.fnst@fujitsu.com>
Cc: "Arunprasad Rajkumar" <ar.arunprasad@gmail.com>,
pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2025-12-16T23:12:34Z
Lists: pgsql-hackers
Attachments
- v1-0001-Fix-unsupported-relations-for-publications.patch (text/x-patch) patch v1-0001
On Tue, Dec 16, 2025, at 6:34 AM, Amit Kapila wrote: > > Prohibiting all commands sounds too restrictive in all cases (FOR ALL > TABLES, FOR TABLE, etc.). It would be better if we can disallow > creating a publication when the user explicitly adds such a relation > in a FOR TABLE publication, otherwise raise a WARNING and don't make > it part of publication. The behavior should be the same for both > partition and inherited tables. > WFM. The attached patch checks the partitions too. The behavior is similar to inherited tables. However, I didn't understand the "otherwise" part. Are you suggesting to add WARNING in the FOR ALL TABLES and FOR TABLES IN SCHEMA if there is any unsupported relations? -- Euler Taveira EDB https://www.enterprisedb.com/