Seeming contradiction in 22.1 - Mailing list pgsql-docs

From David G. Johnston
Subject Seeming contradiction in 22.1
Date
Msg-id CAKFQuwYdUpjOSUTymjHU9Hp-x50EJKWcQwVtBR4uaJ1TL3sF2Q@mail.gmail.com
Whole thread Raw
In response to Seeming contradiction in 22.1  (PG Doc comments form <noreply@postgresql.org>)
Responses Re: Seeming contradiction in 22.1  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-docs
On Thursday, March 23, 2023, maja zaloznik <maja.zaloznik@gmail.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.
 

pgsql-docs by date:

Previous
From: maja zaloznik
Date:
Subject: Re: Seeming contradiction in 22.1
Next
From: Steve Atkins
Date:
Subject: Certificate authentication docs in multiple places