Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ooBts-0007C8-ON for pgsql-general@arkaria.postgresql.org; Thu, 27 Oct 2022 23:03:00 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ooBtr-0000Mw-Gy for pgsql-general@arkaria.postgresql.org; Thu, 27 Oct 2022 23:02:59 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ooBtr-0000Mm-6T for pgsql-general@lists.postgresql.org; Thu, 27 Oct 2022 23:02:59 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ooBto-0006SW-Tc for pgsql-general@lists.postgresql.org; Thu, 27 Oct 2022 23:02:58 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 29RN2s111104988; Thu, 27 Oct 2022 19:02:54 -0400 From: Tom Lane To: "David G. Johnston" cc: Bryn Llewellyn , Ian Lawrence Barwick , pgsql-general list Subject: Re: =?UTF-8?Q?Re=3A_Seeking_the_correct_term_of_art_for_the_=28unique=29?= =?UTF-8?Q?_role_that_is_usually_called_=22postgres=22=E2=80=94and_the_mental_mod?= =?UTF-8?Q?el_that_underlies_it_all?= In-reply-to: References: <8A2C8B1B-470B-42F9-9694-C1EDDAC06266@yugabyte.com> <5C47A318-F265-4A64-B306-C4019F499DB8@yugabyte.com> Comments: In-reply-to "David G. Johnston" message dated "Thu, 27 Oct 2022 15:50:35 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1104986.1666911774.1@sss.pgh.pa.us> Date: Thu, 27 Oct 2022 19:02:54 -0400 Message-ID: <1104987.1666911774@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk "David G. Johnston" writes: > Yes, the description for --username probably should be modified to read: > "Selects the user name of the cluster's bootstrap superuser." Yeah, perhaps. The term "bootstrap superuser" is reasonably well established by now --- I count half a dozen uses in our SGML docs and another dozen or so in the code --- and it's certainly more specific than "database superuser". We should probably create a glossary entry for it and then change all the uses of "database superuser" as appropriate. However ... it looks to me like some of those uses just mean to distinguish between Postgres-specific superuser-dom as opposed to whatever the term might mean out in the operating system. But I'm not sure that anybody really uses that term for an OS-level concept on any popular OS, so it feels a bit pedantic as well as confusing. Should we leave those usages alone, or reduce them to just "superuser"? regards, tom lane