Re: Additional info for CREATE ROLE with REPLICATION - Mailing list pgsql-hackers

From Chao Li
Subject Re: Additional info for CREATE ROLE with REPLICATION
Date
Msg-id 8B56D47F-6310-46FE-AF8B-1E58C7399D51@gmail.com
Whole thread Raw
In response to Additional info for CREATE ROLE with REPLICATION  (Marcos Pegoraro <marcos@f10.com.br>)
Responses Re: Additional info for CREATE ROLE with REPLICATION
List pgsql-hackers

> On Nov 26, 2025, at 05:45, Marcos Pegoraro <marcos@f10.com.br> wrote:
>
> When a logical replication is created and a ROLE with REPLICATION clause is used for that, there is no info on [0]
thatthat role needs to have read permission on those tables. CREATE PUBLICATION and CREATE SUBSCRIPTION commands works
asexpected but replication doesn't work, only a "access denied" is added on logs. 
>
> So it would be good to explain that a GRANT is needed.
>
> [0] - https://www.postgresql.org/docs/current/sql-createrole.html
>
> regards
> Marcos
>
> <0001-Master - Additional info for create role with REPLICATION.diff>

Hi Marcos,

The statement you added is correct, however I don’t think it is the right place to add the statement, “create role”
justdescribes how to assign the replication attribute. 

On I found that in logical-replication.html, there is an explanation already:
```
  <para>
   In order to be able to copy the initial table or sequence data, the role
   used for the replication connection must have the <literal>SELECT</literal>
   privilege on a published table or sequence (or be a superuser).
  </para>
```

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







pgsql-hackers by date:

Previous
From: "Euler Taveira"
Date:
Subject: Re: log_min_messages per backend type
Next
From: Fujii Masao
Date:
Subject: Re: [Proposal] Adding TRIM_SPACE option to COPY