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 1urgFg-00Aa4a-Gp for pgsql-hackers@arkaria.postgresql.org; Thu, 28 Aug 2025 17:17:33 +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 1urgFf-0043QB-Um for pgsql-hackers@arkaria.postgresql.org; Thu, 28 Aug 2025 17:17:32 +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 1urgFf-0043Q1-LZ for pgsql-hackers@lists.postgresql.org; Thu, 28 Aug 2025 17:17:32 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1urgFd-002Dxc-2a for pgsql-hackers@postgresql.org; Thu, 28 Aug 2025 17:17:31 +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 57SHHOqh1905133; Thu, 28 Aug 2025 13:17:24 -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: <202508281623.awysrsga4r34@alvherre.pgsql> References: <202508281623.awysrsga4r34@alvherre.pgsql> Comments: In-reply-to =?utf-8?Q?=C3=81lvaro?= Herrera message dated "Thu, 28 Aug 2025 18:23:46 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1905131.1756401444.1@sss.pgh.pa.us> Date: Thu, 28 Aug 2025 13:17:24 -0400 Message-ID: <1905132.1756401444@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: > Thanks, pushed like that. I changed "a database object" to "an SQL > object", because that's a term we have a definition for. > (I also wrote "PostgreSQL" where you had "Postgres". I think it might > be okay now to change the product name in various places here, but it > seems better to do it consistently across the whole page.) LGTM, thanks. (My wording was only meant as a draft ...) regards, tom lane