Re: pg_basebackup ignores the existing data directory permissions

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Stephen Frost <sfrost(at)snowman(dot)net>, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_basebackup ignores the existing data directory permissions
Date: 2019-03-25 22:44:31
Message-ID: 20190325224431.GI2558@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Mar 25, 2019 at 09:08:23AM -0400, Robert Haas wrote:
> If we're going to go with -g {inherit|none|group} then -g inherit
> ought to do what was originally proposed on this thread -- i.e. set
> the directory permissions to match the contents. I don't think that's
> a change that can or should be back-patched, but we should make it
> consistent as part of this cleanup.

No objections from me to do that actually. That's a small
compatibility break, but with the new options it is possible to live
with. Perhaps we should add into initdb the same switch? Except that
"inherit" makes no sense there.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2019-03-25 22:45:13 Re: MacPorts support for "extra" tests
Previous Message Alvaro Herrera 2019-03-25 22:38:52 Re: psql display of foreign keys