Feedback-ID: ie3de48e3:Fastmail
Date: Fri, 22 Aug 2025 11:46:45 +0200
From: =?utf-8?Q?=C3=81lvaro?= Herrera <alvherre@kurilemu.de>
To: Kirill Reshke <reshkekirill@gmail.com>
Cc: jian he <jian.universality@gmail.com>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: misleading error message in ProcessUtilitySlow T_CreateStatsStmt
Message-ID: <202508220946.osn274hnjxez@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <CALdSSPiZtCRJhe=KdPKEmeYNZQe_yhQKVn3QCsfrCiNdOCTP0A@mail.gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/202508220946.osn274hnjxez%40alvherre.pgsql>
Precedence: bulk

On 2025-Aug-21, Kirill Reshke wrote:

> I wouldn’t say this is misleading, but " a single relation" is indeed
> not precise enough. IMO we need a more precise term to distinguish
> regular relation and table func.

I'm not sure.  See the definition of relation in the glossary:
https://www.postgresql.org/docs/18/glossary.html#GLOSSARY-RELATION

  The generic term for all objects in a database that have a name and a
  list of attributes defined in a specific order. Tables, sequences,
  views, foreign tables, materialized views, composite types, and
  indexes are all relations.

  More generically, a relation is a set of tuples; for example, the
  result of a query is also a relation.

  In PostgreSQL, Class is an archaic synonym for relation.

(I wonder why this says "generically" rather than "generally".  Is that
word choice a mistake?)  Maybe in the "For example" clause we can also
mention table functions.

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/