| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, 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-20 15:54:17 |
| Message-ID: | f0e19b7b-4d0e-b937-a3e5-8127ff405031@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2019-03-18 16:45, Robert Haas wrote:
>> 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.
> So you want to default to no group access regardless of the directory
> permissions, with an option to enable group access that must be
> explicitly specified? That seems like a reasonable option to me; note
> that initdb does seem to chdir() an existing directory.
I think that would have been my preference, but PG11 is already shipping
with the current behavior, so I'm not sure whether that should be changed.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrey Borodin | 2019-03-20 15:58:04 | Re: Special role for subscriptions |
| Previous Message | Alvaro Herrera | 2019-03-20 15:53:30 | Re: partitioned tables referenced by FKs |