Re: initdb --allow-group-access behaviour in windows - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: initdb --allow-group-access behaviour in windows
Date
Msg-id 20190201081437.GK2179@paquier.xyz
Whole thread Raw
In response to initdb --allow-group-access behaviour in windows  (Haribabu Kommi <kommi.haribabu@gmail.com>)
Responses Re: initdb --allow-group-access behaviour in windows  (David Steele <david@pgmasters.net>)
List pgsql-hackers
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.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: reloption to prevent VACUUM from truncating empty pages at theend of relation
Next
From: "Kato, Sho"
Date:
Subject: Speeding up creating UPDATE/DELETE generic plan for partitionedtable into a lot