| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | 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-18 15:35:56 |
| Message-ID: | dc6e2c0f-762b-079c-a951-5766ab2ec5cd@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2019-03-18 14:47, Robert Haas wrote:
>> Based on the feedback gathered, having a separate option to enforce
>> the default and not touching the behavior implemented until now,
>> sounds fine to me.
> That's not what I'm proposing. I think the behavior implemented until
> now is not best, because the files within the directory should inherit
> the directory's permissions, not the remote side's permissions.
I'm strongly in favor of keeping initdb and pg_basebackup options
similar and consistent. They are both ways to initialize data directories.
You'll note that initdb does not behave the way you describe. It's not
unreasonable behavior, but it's not the way it currently works.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2019-03-18 15:45:05 | Re: pg_basebackup ignores the existing data directory permissions |
| Previous Message | Robert Haas | 2019-03-18 15:31:26 | Re: BUG #15641: Autoprewarm worker fails to start on Windows with huge pages in use Old PostgreSQL community/pgsql-bugs x |