From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | chiru r <chirupg(at)gmail(dot)com> |
Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, John R Pierce <pierce(at)hogranch(dot)com>, Forums postgresql <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg_basebackup issue |
Date: | 2017-04-23 15:44:47 |
Message-ID: | d653782a-25d7-8f3b-9293-6e2d11ce8a0e@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 04/23/2017 04:52 AM, chiru r wrote:
> Thank you for your reply.
>
> I agree, However we are planning, users not to have any direct
> privileges on database objects or default roles(like
> SUPERUSER,CREATEDB,REPLICATION..etc) in postgres.
>
> looking to create users(LOGIN) only and Grant all the privileges through
> roles like below.
>
> *Steps: *
> Create User
> Create role
> GRANT required privileges/default attributes(SUPERUSER,REPLICATION etc)
> to Role
> GRANT role to Users.
>
> So,If I follow above process I am not able to do pg_basebackup.
> Now I have only options left either I have to use postgres user or
> create a user directly with replication role(Which we are not interested
> in).
>
> In future is there possibility to allow a user(using above steps) to do
> pg_basebackup?.
That would be a Postgres developer question/answer. Many of the
developers are on this list and may respond at some point. If you want
to put the question directly to the developers I would suggest either:
1) Posting to --hackers (https://www.postgresql.org/list/pgsql-hackers/)
2) Filing a bug report:
https://www.postgresql.org/account/login/?next=/account/submitbug/
>
>
> Thanks,
> Chiru
>
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2017-04-23 15:57:14 | Re: pg_basebackup issue |
Previous Message | Adrian Klaver | 2017-04-23 15:38:10 | Re: Not sure this should be asked here but... |