| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | "Shinoda, Noriyoshi" <noriyoshi(dot)shinoda(at)hpe(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [WIP] Document update for Logical Replication security |
| Date: | 2018-04-11 13:13:56 |
| Message-ID: | 9f1dbb62-7205-d21a-ede4-68c940fb88e2@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/3/18 07:35, Shinoda, Noriyoshi wrote:
> Hi, Hackers,
>
> The attached patch adds the following information to the document on Logical Replication.
> About the requirement of connection role of Logical Replication, written in 31.7 of the manual is as follows.
> --
> The role used for the replication connection must have the REPLICATION attribute.
> --
> However, the Logical Replication connection role also requires the LOGIN attribute.
> And, for initial snapshots of Logical Replication, the connection role requires SELECT privilege on the replication target table, but it is not described in the manual.
Committed, thanks.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2018-04-11 13:21:07 | Re: segmentation fault in pg head with SQL function. |
| Previous Message | Peter Eisentraut | 2018-04-11 12:40:45 | Re: pgbench doc typos |