From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Eric Hanson <eric@aquameta.com>
Cc: Peter Eisentraut <peter@eisentraut.org>
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: "name" vs "alias" in datatype table
Date: Wed, 29 Nov 2023 17:42:54 +0100
Message-ID: <202311291642.xumbxwgwquip@alvherre.pgsql> (raw)
In-Reply-To: <308440.1701275206@sss.pgh.pa.us>
On 2023-Nov-29, Tom Lane wrote:
> Eric Hanson <eric@aquameta.com> writes:
> > The larger point being, the "name" vs "alias" paradigm presented in this
> > table does not accurately represent PostgreSQL, and conveys an inaccurate
> > picture of the relationship between type names. int4 is not an "alias".
>
> I agree that this could be improved, mainly because it's far from
> clear what the internal name of each type is (and there's at least
> one case where the internal name is not shown at all).
Maybe we could split this into multiple *tables*. The main one would be
what we already have except the aliases column is removed, and serial
types removed; the second table would list serial pseudo-types, without
aliases; the third one would have unofficial names (internal names and
other aliases) for types listed in the other two.
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"The ability of users to misuse tools is, of course, legendary" (David Steele)
https://postgr.es/m/11b38a96-6ded-4668-b772-40f992132797@pgmasters.net
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: alvherre@alvh.no-ip.org, tgl@sss.pgh.pa.us, eric@aquameta.com, peter@eisentraut.org, pgsql-docs@lists.postgresql.org
Subject: Re: "name" vs "alias" in datatype table
In-Reply-To: <202311291642.xumbxwgwquip@alvherre.pgsql>
* 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