From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
---|---|
To: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: Roles for pg_basebackup |
Date: | 2020-04-28 08:15:36 |
Message-ID: | BEDCD8D3-D360-45AD-A452-C77C287B7DBF@yesql.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
> On 28 Apr 2020, at 07:22, Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> wrote:
>
> On 2020/04/28 13:37, Michael Paquier wrote:
>> On Mon, Apr 27, 2020 at 12:16:41PM +0200, Daniel Gustafsson wrote:
>>> Based on a recent conversation about backups I had I propose a small tweak to
>>> the pg_basebackup documentation. Listing the user types in the reverse order
>>> from today, putting superuser last, makes it IMO a little clearer that a
>>> REPLICATION role is preferrable to using a superuser for running backups.
>> Makes sense to me. We do that in logical-replication.sgml as well as
>> pg_rewind.sgml (the latter outlines superuser rights last).
>
> Seems there are other documentations having the similar description,
> for example, pg_receivewal.sgml, func.sgml and high-availability.sgml.
> Isn't it better to update also them at the same time?
That doe make sense. I've updated the places where I think a user configuring
the system might conceivably infer a preference from the order, but have left
the other ones as is.
cheers ./daniel
Attachment | Content-Type | Size |
---|---|---|
pg_basebackup_user-v2.diff | application/octet-stream | 2.9 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2020-04-28 18:19:06 | Re: Documentation: 21.5. Default Roles |
Previous Message | Fujii Masao | 2020-04-28 05:22:03 | Re: Roles for pg_basebackup |