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 1qvP7x-004ysK-51 for pgsql-docs@arkaria.postgresql.org; Tue, 24 Oct 2023 21:39: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 1qvP7v-00DdrA-Nm for pgsql-docs@arkaria.postgresql.org; Tue, 24 Oct 2023 21:39: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 1qvP7v-00Ddr1-Fn for pgsql-docs@lists.postgresql.org; Tue, 24 Oct 2023 21:39:51 +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 1qvP7s-002XDP-8p for pgsql-docs@lists.postgresql.org; Tue, 24 Oct 2023 21:39: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=VK7U2gZX7O6UNb/DC/SFkMHaFNj7nu8ZK2/ybc0p69k=; b=u+Qe7ppGTIGrxvIZPeSJcGBSjE HtEj6jnE0guykl7qzaT8UthVemhFFZNbHLxQ/XUY5i7SvxkskraviexArcpDhB2Esu8T1/Cmc2SPO +DhaTsOgCcw6j9snKGJOnUNinqXyQ/GDX4Zw+Gzcn0esFPO9uv2dtu2Udk6pfSc/WD8KcGQ+FejmH qHY8C2HYHML5oAwQDiHWu6DiDrhxvx4vTTAGkQKGkgX7aRqdIW6EaupgUtamr5LvC2ZlDpNf615Q6 4L23hg637MAC1tmi0+KNC4X6iY6/QBhe+Q/YFjMXXOQAehm3zubGgyrRiuZrnqYAjJ62wc8ZsH1lV MnVfOY5Q==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1qvP7p-00B3oc-2m; Tue, 24 Oct 2023 17:39:45 -0400 Date: Tue, 24 Oct 2023 17:39:45 -0400 From: Bruce Momjian To: Laurenz Albe Cc: xinyyc+postgres@gmail.com, pgsql-docs@lists.postgresql.org Subject: Re: Getting started Message-ID: References: <167069800755.1903.2797040477164919245@wrigleys.postgresql.org> <29785cbd957449e98c03a77b6b9fb41970a4f1ca.camel@cybertec.at> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <29785cbd957449e98c03a77b6b9fb41970a4f1ca.camel@cybertec.at> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk xOn Mon, Dec 12, 2022 at 08:20:03AM +0100, Laurenz Albe wrote: > On Sat, 2022-12-10 at 18:46 +0000, PG Doc comments form wrote: > > The following documentation comment has been logged on the website: > > > > Page: https://www.postgresql.org/docs/15/user-manag.html > > Description: > > > > https://www.postgresql.org/docs/current/tutorial-createdb.html > > > > The "getting started" page skips right from the installing to already having > > started the program, but on linux machines, you cannot start psql without > > inputting a special command, "sudo -u postgres psql".  Typing psql will make > > the program tell you that your username doesn't exist, and you can't create > > a username for psql without starting psql first.  I had to search somewhere > > else to learn that I had to start psql with that special command.  > > Yes, the "initdb" step is missing. > > If we had that, it would be clear that the rest of the chapter assumes that > you are running shell commands with an operating system user whose name > is identical to the bootstrap superuser. I looked at this and initdb is mentioned in the installation section, and an incorrect user name is mentions as part of craetedb failure. I don't see what we can add to improve things here. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Only you can decide what is important to you.