From: | Ian Lawrence Barwick <barwick(at)gmail(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(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-10-27 02:10:58 |
Message-ID: | CAB8KJ=hvD3J-FCzP2Ley7nux9Kh5a8gsZCg1jV6X8rSJbCERCg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
2022年10月27日(木) 11:00 David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>:
>
> On Wed, Oct 26, 2022 at 6:33 PM Bryn Llewellyn <bryn(at)yugabyte(dot)com> 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.
>
>
> Don't think it's documented but I like "bootstrap user" which I've seen bandied about here a bit.
"bootstrap superuser" is also mentioned a few times in the docs, see e.g.:
https://www.postgresql.org/docs/devel/sql-grant.html
This recent commit: e530be2c5ce77475d56ccf8f4e0c4872b666ad5f [1] might
also be of interest
to anyone considering the "special-ness" of this role.
Ian Barwick
From | Date | Subject | |
---|---|---|---|
Next Message | Misty Peters (MistyLynn) | 2022-10-27 02:22:25 | Re: Seeking the correct term of art for the (unique) role that is usually called "postgres"—and the mental model that underlies it all |
Previous Message | David G. Johnston | 2022-10-27 02:00:10 | Re: Seeking the correct term of art for the (unique) role that is usually called "postgres"—and the mental model that underlies it all |