Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qlcm5-003f8y-Cc for pgsql-docs@arkaria.postgresql.org; Wed, 27 Sep 2023 22:12:53 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qlcl4-006AH9-Lw for pgsql-docs@arkaria.postgresql.org; Wed, 27 Sep 2023 22:11:51 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qlcl4-006AGx-DW for pgsql-docs@lists.postgresql.org; Wed, 27 Sep 2023 22:11:50 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qlcl1-007yDO-KH for pgsql-docs@lists.postgresql.org; Wed, 27 Sep 2023 22:11:50 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2023062407; h=In-Reply-To:Content-Transfer-Encoding:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-ID:Content-Description; bh=UxtjyzQFPYkz0Zf+FgKzff6xG7dSnKJau6O2ZSPblgI=; b=zK/4BgcGn8LGDe7xAFkT8Ei5On oqAHsbE7hDWuKuU/Uxz/t4IRjR6QeR9hdegUis7UVdeQ3YFythlnQdHLsD/gaPq/Nq4qRzNDtPk/i xS1CnYMlN+XjYracLRPcARf4ODZEA1o0IohH2Yv0q+4L8USHCJj/Gjc/YUhczJlc5HMPDEjqyliLR YgypSm6Zgr/vFSRPWoCHqez/7qz2t0QeQf0hjbZmuyZ1U9+01DPnA2exnV/ZwwvuVVf1ReYtaeP8n L228WXs0lev+HSGYHIucopdQaw/ytom5pH/XcYJ0OfdnOuK07eW0QG81D56oRn93vH9VZytGmugWA XZAmulbg==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1qlcky-006rwb-2v; Wed, 27 Sep 2023 18:11:44 -0400 Date: Wed, 27 Sep 2023 18:11:44 -0400 From: Bruce Momjian To: maja zaloznik Cc: Tom Lane , "David G. Johnston" , pgsql-docs@lists.postgresql.org Subject: Re: Seeming contradiction in 22.1 Message-ID: References: <167931662853.3349090.18217722739345182859@wrigleys.postgresql.org> <1821386.1679584161@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="aBBcbP3a9eu4TpC5" Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --aBBcbP3a9eu4TpC5 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit 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 was doing something outside the purview of > the postgres documentation. > > To me the last sentence would be clearer if it read something like: > > "Most packagers will name this role `postgres` by default, but this is not > required". > > That way it avoids the passive tense which leaves some ambiguity as to who or > what and when is naming this superuser. I think the paragraph was trying to do too much so I simplified it, patch attached. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Only you can decide what is important to you. --aBBcbP3a9eu4TpC5 Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="bootstrap.diff" diff --git a/doc/src/sgml/user-manag.sgml b/doc/src/sgml/user-manag.sgml new file mode 100644 index 27c1f3d..92a299d *** a/doc/src/sgml/user-manag.sgml --- b/doc/src/sgml/user-manag.sgml *************** SELECT rolname FROM pg_roles WHERE rolca *** 103,113 **** In order to bootstrap the database system, a freshly initialized system always contains one predefined login-capable role. This role ! is always a superuser, and by default it will have the same name as the operating system user that initialized the ! database cluster, unless another name is specified while ! running initdb. ! It is common, but not required, to arrange for this role to be named postgres. In order to create more roles you first have to connect as this initial role. --- 103,112 ---- In order to bootstrap the database system, a freshly initialized system always contains one predefined login-capable role. This role ! is always a superuser, and it will have the same name as the operating system user that initialized the ! database cluster with initdb unless a different name ! is specified. This role is often named postgres. In order to create more roles you first have to connect as this initial role. --aBBcbP3a9eu4TpC5--