tutorial
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/18/tutorial-accessdb.html
Description:
In the guide, you provide examples of creating the mydb database and taking
the first steps with it.
This raises the question: why does psql display:
mydb=>
Doesn’t that mean someone created this database and granted access to it?
(Because if it was you)—then you know how to grant access to a database and
create a user—so it turns out you’re an experienced user, but if you really
are: you wouldn’t be reading this section of the manual, because then you’d
be wondering—how did you manage to compile version 18.6 with the gcc
compiler (4.9.2-10) (from 2007)?
mydb=> SELECT version();
version
------------------------------------------------------------------------------------------
PostgreSQL 18.6 on x86_64-pc-linux-gnu, compiled by gcc (Debian 4.9.2-10)
4.9.2, 64-bit
(1 row)
As always, you want to follow the commands step by step from the
documentation—but so many questions remain.
Section 2.1. Introduction provides the following command:
mydb=> \i basics.sql
What do you think the user should see (what should they learn)? What will
remain in the database?
Let’s hope that, over time, navigating the documentation will become easier
and more user-friendly.
On Thu, Aug 27, 2026 at 10:22 AM PG Doc comments form <
noreply@postgresql.org> wrote:
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/18/tutorial-accessdb.html
Description:In the guide, you provide examples of creating the mydb database and taking
the first steps with it.This raises the question: why does psql display:
mydb=>
Doesn’t that mean someone created this database and granted access to it?
Yes, the user supposedly did when performing the exercise in chapter 1.3
What do you think the user should see (what should they learn)? What will
remain in the database?Let’s hope that, over time, navigating the documentation will become easier
and more user-friendly.
That becomes more likely if people like you who wish to see this better
future suggest patches to make it happen.
Personally, I'd rather remove the tutorial from the core project and let it
be a more accessible community effort via the wiki. The legacy of it being
based upon someone possessing the source code is understandable given the
open source nature of the project but doesn't really fit today's reality.
On that front - if said wiki existed (and there really is no one stopping
it from becoming reality) and was on par in content with the documentation
the argument to simply stop maintaining the tutorial in the docs would be
possible to make.
David J.
Yes, the user supposedly did that while working through the exercise in
Chapter 1.3
mydb=>
How did the user become a regular user rather than the database owner??? (
mydb=# )
чт, 27 авг. 2026 г. в 18:03, David G. Johnston <david.g.johnston@gmail.com>:
Show quoted text
On Thu, Aug 27, 2026 at 10:22 AM PG Doc comments form <
noreply@postgresql.org> wrote:The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/18/tutorial-accessdb.html
Description:In the guide, you provide examples of creating the mydb database and
taking
the first steps with it.This raises the question: why does psql display:
mydb=>
Doesn’t that mean someone created this database and granted access to it?
Yes, the user supposedly did when performing the exercise in chapter 1.3
What do you think the user should see (what should they learn)? What will
remain in the database?Let’s hope that, over time, navigating the documentation will become
easier
and more user-friendly.That becomes more likely if people like you who wish to see this better
future suggest patches to make it happen.Personally, I'd rather remove the tutorial from the core project and let
it be a more accessible community effort via the wiki. The legacy of it
being based upon someone possessing the source code is understandable given
the open source nature of the project but doesn't really fit today's
reality. On that front - if said wiki existed (and there really is no one
stopping it from becoming reality) and was on par in content with the
documentation the argument to simply stop maintaining the tutorial in the
docs would be possible to make.David J.