Re: initdb --allow-group-access behaviour in windows

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: 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 08:14:37
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: 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?


In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Kato, Sho 2019-02-01 08:16:11 Speeding up creating UPDATE/DELETE generic plan for partitioned table into a lot
Previous Message Laurenz Albe 2019-02-01 08:11:50 Re: reloption to prevent VACUUM from truncating empty pages at the end of relation