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 1upU2c-0064Dg-7C for pgsql-hackers@arkaria.postgresql.org; Fri, 22 Aug 2025 15:50:59 +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 1upU2b-007IHG-J6 for pgsql-hackers@arkaria.postgresql.org; Fri, 22 Aug 2025 15:50:58 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1upU2b-007IH8-9c for pgsql-hackers@lists.postgresql.org; Fri, 22 Aug 2025 15:50:57 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1upU2Z-001IbC-2U for pgsql-hackers@postgresql.org; Fri, 22 Aug 2025 15:50:57 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 57MFoqfm1885538; Fri, 22 Aug 2025 11:50:52 -0400 From: Tom Lane To: =?utf-8?Q?=C3=81lvaro?= Herrera cc: Kirill Reshke , jian he , PostgreSQL-development Subject: Re: misleading error message in ProcessUtilitySlow T_CreateStatsStmt In-reply-to: <202508221535.gixsh3lgyy2z@alvherre.pgsql> References: <202508221535.gixsh3lgyy2z@alvherre.pgsql> Comments: In-reply-to =?utf-8?Q?=C3=81lvaro?= Herrera message dated "Fri, 22 Aug 2025 17:35:20 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1885536.1755877852.1@sss.pgh.pa.us> Date: Fri, 22 Aug 2025 11:50:52 -0400 Message-ID: <1885537.1755877852@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk =?utf-8?Q?=C3=81lvaro?= Herrera writes: > Yeah, AFAIR I wrote it (or at least heavily edited the original to get > to that), and I was trying to convey exactly those two ideas. If you > want to propose improvements, they're very welcome. Hmmm ... maybe something like Mathematically, a "relation" is a set of tuples; this is the sense meant in the term "relational database". In Postgres, "relation" is commonly used to mean a database object that has 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. A relation in this sense is a container or descriptor for a set of tuples. "Class" is an alternative but archaic term. The system catalog pg_class holds an entry for each Postgres relation. regards, tom lane