"David G. Johnston" writes:
> Or just the bit more verbose “user running the initdb command” and don’t
> bother giving it a label, which is basically the approach used in the
> description for initdb anyway.
Or if you want a few more words, "name of the operating-system user
running initdb". I d
On Saturday, January 6, 2024, David G. Johnston
wrote:
> On Saturday, January 6, 2024, Bruce Momjian wrote:
>
>>
>> geteuid() returns the effective user ID of the calling process.
>>
>> so it is not the owner of the data dirctory, but the installation user.
>>
>> I am open to saying that
On Saturday, January 6, 2024, Bruce Momjian wrote:
> On Sat, Jan 6, 2024 at 08:11:14PM -0700, David G. Johnston wrote:
> > On Saturday, January 6, 2024, Bruce Momjian wrote:
> >
> > This commit:
> >
> > commit 910cab820d
> > Author: Alvaro Herrera
> > Da
On Sat, Jan 6, 2024 at 08:11:14PM -0700, David G. Johnston wrote:
> On Saturday, January 6, 2024, Bruce Momjian wrote:
>
> This commit:
>
> commit 910cab820d
> Author: Alvaro Herrera
> Date: Fri Nov 18 11:59:26 2022 +0100
>
> Add gloss
On Saturday, January 6, 2024, Bruce Momjian wrote:
> This commit:
>
> commit 910cab820d
> Author: Alvaro Herrera
> Date: Fri Nov 18 11:59:26 2022 +0100
>
> Add glossary entries related to superusers
>
> Extracted from a more ambitious patch.
>
>
This commit:
commit 910cab820d
Author: Alvaro Herrera
Date: Fri Nov 18 11:59:26 2022 +0100
Add glossary entries related to superusers
Extracted from a more ambitious patch.
Author: David G. Johnston
