On Wed, Sep 27, 2023 at 06:11:44PM -0400, Bruce Momjian wrote:
> On Thu, Mar 23, 2023 at 05:45:03PM +0100, maja zaloznik wrote:
> > Thanks David, this is very helpful!
> >
> > I would have to agree with Tom, that while technically true, the text could
> > be
> > reworded. namely it was not
On Thu, Mar 23, 2023 at 05:45:03PM +0100, maja zaloznik wrote:
> Thanks David, this is very helpful!
>
> I would have to agree with Tom, that while technically true, the text could be
> reworded. namely it was not obvious to me that i had used a 'packager' to
> install the clusters and therefore
Thanks David, this is very helpful!
I would have to agree with Tom, that while technically true, the text could
be reworded. namely it was not obvious to me that i had used a 'packager'
to install the clusters and therefore was doing something outside the
purview of the postgres documentation.
"David G. Johnston" writes:
> 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,
Thanks for your reply David,
i think you are right about the natural way to interpret the text -
although if that was the intention it could probably be worded more clearly
e.g. by adding 'renamed' or 'instead' or both.
My issue is that - at least as far as i can recall - the default superuser
Thanks David,
sorry for pushing this - I don't mean to imply what you say is not true,
but would like to understand how it can be true and at the same time users
like me are convinced otherwise. The internet is chock full of instructions
and tutorials mentioning the default superuser is postgres,
On Thursday, March 23, 2023, maja zaloznik 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
On Wed, Mar 22, 2023 at 3:41 PM maja zaloznik
wrote:
> My issue is that - at least as far as i can recall - the default superuser
> was already named postgres
>
There is no compiled-in default for the name of the bootstrap superuser.
It is chosen during initdb using the algorithm described
On Monday, March 20, 2023, PG Doc comments form
wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/15/database-roles.html
> Description:
>
> In chapter 22.1 the following text seems to imply the role will have "the
> same name
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/15/database-roles.html
Description:
In chapter 22.1 the following text seems to imply the role will have "the
same name as the user that initialised" it and also the "role will be named
10 matches
Mail list logo
