| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, chris+postgresql(at)qwirx(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org, pgsql-hackers(at)lists(dot)postgresql(dot)org, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Subject: | Re: Logical replication subscription owner |
| Date: | 2020-05-08 05:02:11 |
| Message-ID: | 20200508050211.GA6945@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
On 2020-May-07, Tom Lane wrote:
> FWIW, I would argue that LOGIN permits logging in on a regular SQL
> connection, while REPLICATION should permit logging in on a
> replication connection, and there's no reason for either to depend on
> or require the other.
I agree with this.
> >> Also- what about per-database connections? Does having REPLICATION mean
> >> you get to override the CONNECT privileges on a database, if you're
> >> connecting for the purposes of doing logical replication?
>
> No, why would it? Should LOGIN privilege mean you can override
> CONNECT? That's nonsense. You need the respective privilege
> to connect with the protocol you want to connect with, and you
> also need CONNECT on the DB you want to connect to.
And this.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro Horiguchi | 2020-05-08 06:03:26 | Re: Logical replication subscription owner |
| Previous Message | Tom Lane | 2020-05-08 03:30:23 | Re: Logical replication subscription owner |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andy Fan | 2020-05-08 05:08:50 | Re: Implementing Incremental View Maintenance |
| Previous Message | Amit Kapila | 2020-05-08 04:36:33 | Re: Fix pg_buffercache document |