"name" vs "alias" in datatype table

From: PG Doc comments form <noreply(at)postgresql(dot)org>
To: pgsql-docs(at)lists(dot)postgresql(dot)org
Cc: eric(at)aquameta(dot)com
Subject: "name" vs "alias" in datatype table
Date: 2023-11-23 20:51:53
Message-ID: 170077271331.398198.16997446522206025709@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

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.

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Erki Eessaar 2023-11-24 11:04:09 INFORMATION_SCHEMA.routine_column_usage
Previous Message David G. Johnston 2023-11-23 15:35:39 Re: Mention that there will be no feedback.