Horton

Re: Improve documentation of publication privilege checks

Chao Li <li.evan.chao@gmail.com>

View thread
From: Chao Li <li.evan.chao@gmail.com>
To: Shlok Kyal <shlok.kyal.oss@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-12-23T09:16:47Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Doc: Clarify publication privilege requirements.


> On Dec 23, 2025, at 16:59, Shlok Kyal <shlok.kyal.oss@gmail.com> wrote:
> 
> Hi Hackers,
> 
> While reviewing the Security section of the logical replication
> documentation, I felt that the description of privilege requirements
> for publications is ambiguous, and clarity could be improved by
> explicitly mentioning the associated SQL syntax. Thoughts?
> 
> Thanks,
> Shlok Kyal
> <v1-0001-Improve-documentation-of-publication-privilege-ch.patch>

I have no objection to this patch. Just the new phrase sounds a little redundant as “FOR TABLES IN SCHEMA” is mentioned twice back-to-back. I tried to rephrase like:

```
To create a publication that automatically publishes objects using
<literal>FOR ALL TABLES</literal>,
<literal>FOR ALL SEQUENCES</literal>, or
<literal>FOR TABLES IN SCHEMA</literal>, the user must be a superuser.
Likewise, adding tables using <literal>TABLES IN SCHEMA</literal> with
<command>ALTER PUBLICATION</command> requires superuser privileges.
To add individual tables to a publication, the user must have ownership rights on the table.
```

I am open if you accept my suggestion or try to enhance the phrase on your own.

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/