Re: Improve documentation of publication privilege checks

From: Peter Smith <smithpb2250(at)gmail(dot)com>
To: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
Cc: Shlok Kyal <shlok(dot)kyal(dot)oss(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Improve documentation of publication privilege checks
Date: 2025-12-23 23:42:53
Message-ID: CAHut+PvombcsmxHgAe-WzjBqNdAr9REePP=xXM_cvd_nS5C-dA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Shlok/Chao-San.

How about this alternative wording:

<para>
To create a publication using any of <literal>FOR ALL TABLES</literal>,
<literal>FOR ALL SEQUENCES</literal>, or
<literal>FOR TABLES IN SCHEMA</literal>, the user must be a superuser.
To alter a publication using <literal>ADD TABLE</literal>, the user must
have ownership rights on the table. To alter a publication using
<literal>ADD TABLES IN SCHEMA</literal>, the user must be a superuser.
</para>

IMO this is both simpler and more consistent. PSA a diff for the same.

======
Kind Regards,
Peter Smith.
Fujitsu Australia

Attachment Content-Type Size
PS_wording.diff application/octet-stream 1.1 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Chao Li 2025-12-23 23:53:26 Re: Fix wrong reference in pg_overexplain's doc
Previous Message Chao Li 2025-12-23 23:40:19 Re: DOCS - "\d mytable" also shows any publications that publish mytable