From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | Bryn Llewellyn <bryn(at)yugabyte(dot)com>, pgsql-general list <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Seeking the correct term of art for the (unique) role that is usually called "postgres"—and the mental model that underlies it all |
Date: | 2022-11-29 16:31:19 |
Message-ID: | Y4Yz11OAcO16JRtE@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Oct 26, 2022 at 09:57:50PM -0700, Adrian Klaver wrote:
> On 10/26/22 18:33, Bryn Llewellyn wrote:
> > The descriptive designation "the role that owns the SQL part of the
> > implementation of PostgreSQL" is too much of a mouthful for daily use.
> > And anyway, this notion captures only part of the story that makes
> > "postgres" uniquely what it is—at least on Ubuntu.
> >
> > MORE...
> >
> > Here's what my empirical observations told me:
> >
> > It's easy to characterize this role by describing the way that you get
> > it and the conspicuous unique emergent properties that it has.
> >
> > * You specify its name using the flag that's shown thus in response to
> > "initdb —help"
> >
> > -U, --username=NAME database superuser name
>
> How much time would it have taken to go to the docs?:
>
> https://www.postgresql.org/docs/current/app-initdb.html
I know I am replying late here, but isn't it the database _cluster_
superuser?
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Embrace your flaws. They make you human, rather than perfect,
which you will never be.
From | Date | Subject | |
---|---|---|---|
Next Message | Вадим Самохин | 2022-11-29 16:39:42 | postgresql 13.1: precision of spatial operations |
Previous Message | Pavel Stehule | 2022-11-29 16:28:16 | Re: plpgsql_check_function issue after upgrade |