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 1rGNuL-00F1EO-28 for pgsql-admin@arkaria.postgresql.org; Thu, 21 Dec 2023 18:36: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 1rGNuJ-00CiKC-Gz for pgsql-admin@arkaria.postgresql.org; Thu, 21 Dec 2023 18:36:31 +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 1rGNuJ-00CiK4-5j for pgsql-admin@lists.postgresql.org; Thu, 21 Dec 2023 18:36:31 +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 1rGNuG-00DDTA-R9 for pgsql-admin@lists.postgresql.org; Thu, 21 Dec 2023 18:36:30 +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 3BLIaQIN796633; Thu, 21 Dec 2023 13:36:26 -0500 From: Tom Lane To: richard coleman cc: Pgsql-admin Subject: Re: Case sensitive grant statements in pg14? In-reply-to: References: Comments: In-reply-to richard coleman message dated "Thu, 21 Dec 2023 13:26:03 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <796631.1703183786.1@sss.pgh.pa.us> Date: Thu, 21 Dec 2023 13:36:26 -0500 Message-ID: <796632.1703183786@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk richard coleman writes: > grant create, usage on schema {schema_name} to {role}; > fails with the error: > ERROR: syntax error at or near "{role}" > but by changing the capitalization of the statement to: > GRANT CREATE, USAGE ON SCHEMA {schema_name} TO {role}; > completes successfully. What are you expecting will replace "{role}" with something valid? Whatever that is is apparently somehow dependent on the context being upper-case. regards, tom lane