| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net>, Ian Barwick <ian(dot)barwick(at)2ndquadrant(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-committers <pgsql-committers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pgsql: Prevent running pg_basebackup as root |
| Date: | 2020-02-07 02:07:02 |
| Message-ID: | 20200207020702.o64l2i4mkv5us6oy@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Hi,
On 2020-02-06 13:02:07 +0100, Magnus Hagander wrote:
> I agree with Stephen that this seems to be misguided, and my vote is
> to revert.
+1. I honestly don't think we should increase the number of "root
disallowed" tools unless actually necessary.
Maybe that's looking too far into the future, but I'd like to see
improvements to pg_basebackup that make it integrate with root requiring
tooling, to do more efficient base backups. E.g. having pg_basebackup
handle start/stop backup and WAL handling, but do the actual backup of
the data via a snapshot mechanism (yes, one needs start/stop backup in
the general case, for multiple FSs), would be nice.
Btw, I think it's good form in a discussion like this to CC the original
author. I'll also add a reference to this discussion from the -hackers
thread.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ian Barwick | 2020-02-07 02:23:56 | Re: pgsql: Prevent running pg_basebackup as root |
| Previous Message | Michael Paquier | 2020-02-07 01:55:30 | Re: pgsql: Prevent running pg_basebackup as root |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2020-02-07 02:08:08 | Re: Prevent pg_basebackup running as root |
| Previous Message | Michael Paquier | 2020-02-07 01:55:30 | Re: pgsql: Prevent running pg_basebackup as root |