| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | chiru r <chirupg(at)gmail(dot)com> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(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 02:03:03 |
| Message-ID: | CAKFQuwa0Stfdbify9-xFijzaoQPV9Q_+VF4d7ML=K1CW0yLKXw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Saturday, April 22, 2017, chiru r <chirupg(at)gmail(dot)com> wrote:
> Thank you Adrian.
>
> It seems the code is allowing only who has Superuser/Replication role
> directly.
>
> Is there any possibility in future releases they allow both case A & B
> Users able to use pg_basebackup.
>
>
It does not seem wise to introduce inheritance of such
powerful capabilities when for many years now we have not done so. It
seems like reality could be better documented but the present behavior
should stay. I also find the original choice to be quite sane regardless.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | chiru r | 2017-04-23 03:04:17 | Re: pg_basebackup issue |
| Previous Message | chiru r | 2017-04-22 23:44:23 | Re: pg_basebackup issue |