From: PG Doc comments form <noreply@postgresql.org>
To: pgsql-docs@lists.postgresql.org
Cc: eric@aquameta.com
Subject: "name" vs "alias" in datatype table
Date: Thu, 23 Nov 2023 20:51:53 +0000
Message-ID: <170077271331.398198.16997446522206025709@wrigleys.postgresql.org> (raw)
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/16/datatype.html
Description:
I think there could be some clarification of what is a "name" vs. "alias" on
the datatypes table. Right now, what's in the "Aliases" column is sometimes
postgres's internal type (e.g. `pg_catalog.int4`), and sometimes the "pretty
name", (e.g. `integer`).
How about if this table was laid out still as one row per type, but the
columns were "Names" (plural) and "Internal Name" (singular). Names would
contain both "int" and "integer" (neither of which appear in `pg_type`) and
"Internal Name" would contain "pg_catalog.int4", the "real" name. Then you
could also include arrays here, so that `text[]` would appear in the names
column and `pg_catalog._text` would appear in the "Internal Name" column.
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, eric@aquameta.com
Subject: Re: "name" vs "alias" in datatype table
In-Reply-To: <170077271331.398198.16997446522206025709@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