From: PG Doc comments form <noreply@postgresql.org>
To: pgsql-docs@lists.postgresql.org
Cc: matematica.a3k@gmail.com
Subject: Improve "3.6. Inheritance" tutorial
Date: Thu, 01 Oct 2026 18:55:15 +0000
Message-ID: <179088091522.1026193.3570337969572056877@wrigleys.postgresql.org> (raw)
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/18/tutorial-inheritance.html
Description:
I propose the following modifications:
- "... cities. If you're really clever you might invent some scheme like
this:"
I think it's a joke which didn't age well, "Suppose you invent..." should be
better.
- "This works OK as far as querying goes, but it gets ugly when you need to
update several rows, for one thing.
A better solution is this:"
"In this sense, a better solution is:" should be better.
- "In this case, a row of capitals inherits all columns (name, population,
and elevation) from its parent, cities. The type of the column name is text,
a native PostgreSQL type for variable length character strings. The capitals
table has an additional column, state, which shows its state abbreviation.
In PostgreSQL, a table can inherit from zero or more other tables."
This may be refactored into:
"In this case, a row of capitals inherits all columns (name, population, and
elevation) from its parent, cities. The capitals table has an additional
column, state, which shows its state abbreviation.
In PostgreSQL, a table can inherit from zero or more other tables, and a
query can reference either all rows of a table or all rows of a table plus
all of its descendant tables. The latter behavior is the default."
- "which returns:"
"Given the sample data from the PostgreSQL tutorial (see Section 2.1), this
returns::" should be clearer
- "Note
Although inheritance is frequently useful, it has not been integrated with
unique constraints or foreign keys, which limits its usefulness. See Section
5.11 for more detail."
"Inheritance has not been integrated with unique constraints or foreign
keys, which limits its usefulness. See Section 5.11 for a complete
description of the feature." should be more precise
Regards,
Rodrigo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: noreply@postgresql.org, pgsql-docs@lists.postgresql.org, matematica.a3k@gmail.com
Subject: Re: Improve "3.6. Inheritance" tutorial
In-Reply-To: <179088091522.1026193.3570337969572056877@wrigleys.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox