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-20 12:32:54 |
Message-ID: | e1ce2186-dd21-b1d7-9ebc-060728914d67@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 3/18/17 09:31, Petr Jelinek wrote:
>> 0003 Add USAGE privilege for publications
>>
>> a way to control who can subscribe to a publication
>>
> Hmm IIUC this removes ability of REPLICATION role to subscribe to
> publications. I am not quite sure I like that.
Well, this is kind of the way with all privileges. They take away
abilities by default so you can assign them in a more fine-grained manner.
You can still connect as superuser and do anything you want, if you want
a "quick start" setup.
Right now, any replication user connecting can use any publication.
There is no way to distinguish different table groupings or different
use cases, such as partial replication of some tables that should go
over here, or archiving of some other tables that should go over there.
That's not optimal.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2017-03-20 12:33:02 | Re: [COMMITTERS] pgsql: Improve pg_dump regression tests and code coverage |
Previous Message | Rajkumar Raghuwanshi | 2017-03-20 12:21:28 | Re: wait events for disk I/O |