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.98.2) (envelope-from ) id 1xRYdy-000000014up-1a0H for pgsql-docs@arkaria.postgresql.org; Thu, 12 Nov 2026 17:31:26 +0000 Received: from localhost ([127.0.0.1]:47730 helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xRYds-0000000451F-1il4 for pgsql-docs@arkaria.postgresql.org; Thu, 12 Nov 2026 17:31:20 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]:56418) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xROfN-0000000FNBK-0p3Z for pgsql-docs@lists.postgresql.org; Thu, 12 Nov 2026 06:52:13 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xROfK-00000000bLM-21OL for pgsql-docs@lists.postgresql.org; Thu, 12 Nov 2026 06:52:12 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:Cc:From:To:Subject: Content-Transfer-Encoding:MIME-Version:Content-Type:Sender:Content-ID: Content-Description:In-Reply-To:References; bh=SidEKz/XCOwX8+QoZCU7G3/JhNW0sX+lUWE9se/9vak=; b=W9A7YGU9qyXmFLXctWPu9kglyf 8eVrhPa0KDUMxzyxnGseDoHDwJN7nuVhva0wEK13aEKFARS45CRKLYewV/ge2Hur/wYMWTGTbDoeY 8wMTwNHeI3lSVCjpKShyegDwu/DJ8mWnAtf4g2ZOi5R66Y6D9UZ85cieWCEfTrjy8l/fmTHGMW8YT 4RTkuT+0zemZdXyvlSY+nSLDQi+Zm5nh9t2q7s6UdiVjpvMhCJOLH0GuGGs2vtNfAX2w3RGaOlgbY z1dBlUACJrXYudZbjxNkJ8OUKr8iI4EAVsTTmJbL6295w0zrOGEgMv6R04ilpTLiC5/g4zIKHTFXi VnSAvhag==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xROfI-00000001NzW-48zc for pgsql-docs@lists.postgresql.org; Thu, 12 Nov 2026 06:52:09 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xROfD-00000003Xab-12vL for pgsql-docs@lists.postgresql.org; Thu, 12 Nov 2026 06:52:03 +0000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: Clarification on SET SESSION AUTHORIZATION Syntax To: pgsql-docs@lists.postgresql.org From: PG Doc comments form Cc: vishnupalani19@gmail.com Reply-To: vishnupalani19@gmail.com, pgsql-docs@lists.postgresql.org Date: Thu, 12 Nov 2026 06:51:26 +0000 Message-ID: <179446628655.706202.828157255286601648@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/18/sql-set-session-authorization.html Description: Hi Team, In the `SET SESSION AUTHORIZATION` statement, the syntax is defined as: ```sql SET [ SESSION | LOCAL ] SESSION AUTHORIZATION user_name; ``` I would like to clarify whether the following query is valid: ```sql SET SESSION SESSION AUTHORIZATION user_name; ``` Since `SESSION` and `LOCAL` are optional alternatives in the syntax, does the first `SESSION` keyword allow the query to contain two consecutive `SESSION` keywords? If this syntax is not valid, should we update the grammar to the following? ```sql SET [ LOCAL ] SESSION AUTHORIZATION user_name; ``` Please clarify the expected syntax so that we can update the grammar accordingly. Thanks.