| From: | David Steele <david(at)pgmasters(dot)net> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz>, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: initdb --allow-group-access behaviour in windows |
| Date: | 2019-02-01 17:14:19 |
| Message-ID: | c52027ae-b3cd-04ff-e4e9-2d9c96a8abb8@pgmasters.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2/1/19 10:14 AM, Michael Paquier wrote:
> On Fri, Feb 01, 2019 at 05:34:05PM +1100, Haribabu Kommi wrote:
>> As Microsoft windows doesn't support POSIX style of permissions, we
>> always set for the permissions GUC's as not supported in
>> windows. Even the new GUC that is added with --allow-group-access
>> feature also mentioned the same.
>>
>> The initdb --allow-group-access doesn't have any impact on the
>> microsoft windows, so I feel it should be better to write the same
>> in initdb docs?
>
> Sounds right. We may just want an extra sentence in the paragraph
> describing --allow-group-access to mention that this parameter has no
> effect on Windows.
>
>> need a patch?
>
> Always.
Hrm, seems like I missed that. Do you mind writing something that makes
sense to Windows users and I'll have a look?
Thanks,
--
-David
david(at)pgmasters(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2019-02-01 17:42:45 | Re: Is zheap on track for PostgreSQL 12.0? |
| Previous Message | Andres Freund | 2019-02-01 16:24:04 | fast defaults in heap_getattr vs heap_deform_tuple |