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 1r7VDq-005cOV-58 for pgsql-hackers@arkaria.postgresql.org; Mon, 27 Nov 2023 06:35:58 +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 1r7VDo-00B3qq-OE for pgsql-hackers@arkaria.postgresql.org; Mon, 27 Nov 2023 06:35:56 +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 1r7VDo-00B3pj-EX for pgsql-hackers@lists.postgresql.org; Mon, 27 Nov 2023 06:35:56 +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.94.2) (envelope-from ) id 1r7VDh-008jvV-Fh for pgsql-hackers@lists.postgresql.org; Mon, 27 Nov 2023 06:35:55 +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 3AR6ZiEh3772066; Mon, 27 Nov 2023 01:35:44 -0500 From: Tom Lane To: Laurenz Albe cc: Peter Smith , Michael Paquier , Alvaro Herrera , Nathan Bossart , Peter Eisentraut , Daniel Gustafsson , PostgreSQL Hackers Subject: Re: GUC names in messages In-reply-to: References: <202311240953.6linnh7oxsdn@alvherre.pgsql> Comments: In-reply-to Laurenz Albe message dated "Mon, 27 Nov 2023 07:31:50 +0100" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3772064.1701066944.1@sss.pgh.pa.us> Date: Mon, 27 Nov 2023 01:35:44 -0500 Message-ID: <3772065.1701066944@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Laurenz Albe writes: > On Mon, 2023-11-27 at 13:41 +1100, Peter Smith wrote: >> In the documentation and in the guc_tables.c they are all described in >> MixedCase (e.g. "DateStyle" instead of "datestyle"), so I felt the >> messages should use the same case the documentation, which is why I >> changed all the ones you are referring to. > I agree with that decision; we should use mixed case for these parameters. > Otherwise we might get complaints that the following query does not return > any results: > SELECT * FROM pg_settings WHERE name = 'timezone'; Yeah. Like Michael upthread, I've wondered occasionally about changing these names to all-lower-case. It'd surely be nicer if we'd done it like that to begin with. But I can't convince myself that the ensuing user pain would be justified. regards, tom lane