Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r8MJQ-009T9H-Ck for pgsql-docs@arkaria.postgresql.org; Wed, 29 Nov 2023 15:17:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1r8MJO-00BOCC-Tu for pgsql-docs@arkaria.postgresql.org; Wed, 29 Nov 2023 15:17:14 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r8MJO-00BOC2-Hn for pgsql-docs@lists.postgresql.org; Wed, 29 Nov 2023 15:17:14 +0000 Received: from mail-yb1-xb36.google.com ([2607:f8b0:4864:20::b36]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1r8MJM-007xPC-1i for pgsql-docs@lists.postgresql.org; Wed, 29 Nov 2023 15:17:13 +0000 Received: by mail-yb1-xb36.google.com with SMTP id 3f1490d57ef6-dae0ab8ac3eso6143338276.0 for ; Wed, 29 Nov 2023 07:17:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aquameta-com.20230601.gappssmtp.com; s=20230601; t=1701271031; x=1701875831; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=RBQDxK0EmEzfkpfCTsyBoUwHqNCveGY0HEze49D9WG8=; b=sLCBKSMy6CXPnsjBR6AtAZUuf8Gh4ZR/DWQAXqq9JPxS/DH8xLyMZYRX0G1JGIhB/C UTwyasMCpQ61pUWduHoBGyaLUFYbxPodV0la5fsnkMMVclD7FiW1eGMKIQ8tGzjyIo0V HZTSzXbn/E8MExnItN/d8OVcDjbMZitWKp8XcT9/nX/soH5jLS116SEaOBc3gcudwqvT SGXI08w+cBOF4dRhtG1ttLBLqI8FXbwf0oJOzE5KKdsI4MwW85cdcyiT3QyYfUisb5Rl pir+sU76Ff+ax12oqi03YxQxUC088/li2xgpvQz7VA8eNRNyq6Lb0ZyYF7+jrXm541IC pm5w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1701271031; x=1701875831; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=RBQDxK0EmEzfkpfCTsyBoUwHqNCveGY0HEze49D9WG8=; b=k5Jfh6vDMAfpr2DKqwv1EckXbwxgptxG2LdAeC6yLxbMZVmSP5DQTnDea4O+w+J9gS Gv1fzhwU3LwvTM3MqtPGBYq05dBFIL8zCxWehklNagXaxgJD5bqPr3tOmJmjDB+sfT9l 5siQRbx5jWVr3Q3SUnsKTaVxwTVv2nu9dlxuOYvdxVRxA6rzWL21OIIDAk9ogUtRTgfv 5e+PY2Snl8N8WAPgWaDmvzgYNbgUwPqMSOB5H6z/8+IYVHn2qaox8ROoVfo8XqHWIR9A 5caTTGG1T7LGGkY21+kQWyLXSF62offv9eFYzPQzABDWtUPa/CGj+/MdiQ/UhCAQGNim EKlA== X-Gm-Message-State: AOJu0YyNcuU3fVpmAJxUrymd/dRh8A0ReTJ5sj/LH4xFYm734UbFP3Uy +815GMJuG37PuTTCDnPEPf1NVPS1fI6DbZN4jkd6Ui9luQfp8fKB X-Google-Smtp-Source: AGHT+IGPhcczlFDepPIFHNoIkap3eGRb7RCKXQhq/oomr4dAiZYWrU6iNYSMopABrF4U7U/268XOVVGxLrrEEHl7KJc= X-Received: by 2002:a25:8d0b:0:b0:da0:cbff:4e20 with SMTP id n11-20020a258d0b000000b00da0cbff4e20mr16705685ybl.56.1701271031283; Wed, 29 Nov 2023 07:17:11 -0800 (PST) MIME-Version: 1.0 References: <170077271331.398198.16997446522206025709@wrigleys.postgresql.org> <83419ce9-e2ba-46e9-aaff-f6bbe448a327@eisentraut.org> In-Reply-To: From: Eric Hanson Date: Wed, 29 Nov 2023 09:16:57 -0600 Message-ID: Subject: Re: "name" vs "alias" in datatype table To: Peter Eisentraut Cc: pgsql-docs@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000007c94a4060b4c0755" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000007c94a4060b4c0755 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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". On Wed, Nov 29, 2023 at 8:10=E2=80=AFAM Eric Hanson wro= te: > On Wed, Nov 29, 2023 at 7:40=E2=80=AFAM Peter Eisentraut > wrote: > >> On 23.11.23 21:51, PG Doc comments form wrote: >> > 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`). >> >> This appears not to be true. `integer` is not listed as an alias. >> > > Sorry, "int" is, and it is not in pg_type. > --0000000000007c94a4060b4c0755 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
The larger point being, the "name" vs "alia= s" paradigm presented in this table does not accurately represent Post= greSQL, and conveys an inaccurate picture of the relationship between type = names.=C2=A0 int4 is not an "alias".

On Wed, Nov 29, 2023 at 8:10= =E2=80=AFAM Eric Hanson <eric@aquam= eta.com> wrote:
On Wed, Nov 29, 2023 at 7:40=E2=80= =AFAM Peter Eisentraut <peter@eisentraut.org> wrote:
On 23.11.23 21:5= 1, PG Doc comments form wrote:
> I think there could be some clarification of what is a "name"= ; vs. "alias" on
> the datatypes table.=C2=A0 Right now, what's in the "Aliases&= quot; column is sometimes
> postgres's internal type (e.g. `pg_catalog.int4`), and sometimes t= he "pretty
> name", (e.g. `integer`).

This appears not to be true.=C2=A0 `integer` is not listed as an alias.
=

Sorry, "int" is, and it is not i= n pg_type.=C2=A0
--0000000000007c94a4060b4c0755--