| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: logical replication access control patches |
| Date: | 2017-03-22 15:29:06 |
| Message-ID: | 90f71750-b1a6-f667-cd4d-b6fbcd0a879c@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/22/17 08:12, Petr Jelinek wrote:
> On 22/03/17 03:38, Peter Eisentraut wrote:
>> On 3/20/17 15:10, Petr Jelinek wrote:
>>> Hmm but REPLICATION role can do basebackup/consume wal, so how does
>>> giving it limited publication access help? Wouldn't we need some
>>> SUBSCRIPTION role/grant used instead for logical replication connections
>>> instead of REPLICATION for this to make sense?
>>
>> Since we're splitting up the pg_hba.conf setup for logical and physical
>> connections, it would probably not matter.
>
> Hmm yeah I know about that, I am not quite clear on how that change
> affects this.
Well, the explanation for what I had in mind is too complicated to even
put into words, so it's probably not a good idea. ;-)
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2017-03-22 15:37:03 | Re: PATCH: Make pg_stop_backup() archive wait optional |
| Previous Message | Peter Eisentraut | 2017-03-22 15:21:47 | Re: logical replication access control patches |