From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | maja zaloznik <maja(dot)zaloznik(at)gmail(dot)com> |
Cc: | "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
Subject: | Seeming contradiction in 22.1 |
Date: | 2023-03-23 12:25:08 |
Message-ID: | CAKFQuwYdUpjOSUTymjHU9Hp-x50EJKWcQwVtBR4uaJ1TL3sF2Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Thursday, March 23, 2023, maja zaloznik <maja(dot)zaloznik(at)gmail(dot)com> wrote:
>
> My point being that if what you say is true but runs counter to what
> essentially all other instructions on the internet say, it would seem
> prudent to mention this disparity and the reasons for it in the canonical
> documentation, which would be especially valuable for noobs like me.
>
The root issue, IMO, is that all packagers have settled on the convention
of using Postgres for the superuser name, so if one only ever sees that, it
is easy to assume it is some kind of default of the software itself. In
the face of consistent evidence, people not reading the documentation is my
supposed assumption for their ignorance of this point. But reading the
docs, it is clear how the system really works (I.e., the name of the
bootstrap superuser comes is derived at initdb time from the environment
executing initdb).
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Steve Atkins | 2023-03-23 13:33:13 | Certificate authentication docs in multiple places |
Previous Message | maja zaloznik | 2023-03-23 08:36:55 | Re: Seeming contradiction in 22.1 |