| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | Takeshi Ideriha <iderihatakeshi(at)gmail(dot)com> |
| Cc: | Peter Smith <smithpb2250(at)gmail(dot)com>, shveta malik <shveta(dot)malik(at)gmail(dot)com>, Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: DOCS - CREATE PUBLICATION wording re 'ONLY' for partitioned tables. |
| Date: | 2026-10-22 08:14:24 |
| Message-ID: | CAHGQGwHwqW23vT7z-z49i2wCRT3zewWoGk=AqYWDi8xY_srHaw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Oct 20, 2026 at 2:20 PM Takeshi Ideriha
<iderihatakeshi(at)gmail(dot)com> wrote:
> Thank you for addressing my suggestion. V3 looks good to me. I also
> believe the same wording works.
Thanks for updating the patch!
+ For a partitioned table, <literal>ONLY</literal> and <literal>*</literal>
+ have no effect: its partitions are always implicitly considered part of
+ the publication, so they do not need to be added explicitly.
In ALTER PUBLICATION, "table_name" also applies to DROP and EXCEPT,
so seems the original wording needs to account for those cases.
How about:
For a partitioned table, <literal>ONLY</literal> and <literal>*</literal>
have no effect. When a partitioned table is included in a publication,
its partitions are implicitly included as well and need not be added
explicitly. For tables specified in <literal>EXCEPT</literal>, see the
description of
<link linkend="sql-createpublication-params-for-except-table"><literal>EXCEPT</literal></link>
in <xref linkend="sql-createpublication"/>.
</para>
-
<para>
Why is this blank line removed?
Regards,
--
Fujii Masao
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chao Li | 2026-10-22 08:19:01 | Re: [PATCH v1] Fix for bug #19770 : Reject NO INHERIT not-null constraints copied by LIKE to partitioned tables |
| Previous Message | Zhijie Hou | 2026-10-22 07:16:01 | Re: [PG19] Promotion hangs behind a backend blocked on a stuck client |