Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nP7gA-0007IH-Eu for pgsql-hackers@arkaria.postgresql.org; Tue, 01 Mar 2022 18:56:58 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nP7g9-0002Rn-CB for pgsql-hackers@arkaria.postgresql.org; Tue, 01 Mar 2022 18:56:57 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nP7g8-0002Re-7E for pgsql-hackers@lists.postgresql.org; Tue, 01 Mar 2022 18:56:57 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nP7g2-00023W-Rm for pgsql-hackers@postgresql.org; Tue, 01 Mar 2022 18:56:55 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 231D75C01BB; Tue, 1 Mar 2022 13:56:48 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Tue, 01 Mar 2022 13:56:48 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=V8hZYPd/VOA1egxfOHWV+CNEdJmuDfHRSjHX5gIUM js=; b=R4x41rOtVRN+p1/GUlXE5F0ckbYVhLvAmlOixZrmaHYW6ce95qjbH+NuX WqKbCPMAmSQEDt9hs0PTUeCzO4mToh3SGmxpD0tcGe8D/txW/iJj/831imYDEbXn WvGlSmnltmVAQ0I3fp2tJLVXMijOObxjo6eymctVR2TPjiUIkRXAqxYMEyjpyfBJ DpgE9CiRO5gIx6u12f9BrKSLKrKbqgQeunSIoEKdEFGV9iBLaNS7Y2Nx8KSrMnMD d6eS880hB4PCRBX3Nne2jPJHyyTGKUnnD8RD/ytSIqL6Y/YkkFMJwp35fXLR8Pb9 eIlRfRsGvCwGmbF64skUDNFWVpvUQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddruddtvddgudduiecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefkffggfgfuvfhfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvght vghrucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvghnth gvrhhprhhishgvuggsrdgtohhmqeenucggtffrrghtthgvrhhnpeefjeegheetuefhveev udelueeftdejteeiffetvdduhfdtieefgfeutedtveeggfenucevlhhushhtvghrufhiii gvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvghnthhrrghu thesvghnthgvrhhprhhishgvuggsrdgtohhm X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 1 Mar 2022 13:56:46 -0500 (EST) Message-ID: Date: Tue, 1 Mar 2022 19:56:45 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.6.0 Subject: Re: [PATCH] Expose port->authn_id to extensions and triggers Content-Language: en-US To: Jacob Champion , "rjuju123@gmail.com" Cc: "pgsql-hackers@postgresql.org" , "michael@paquier.xyz" , "sfrost@snowman.net" References: <793d990837ae5c06a558d58d62de9378ab525d83.camel@vmware.com> <2e28b12b450f247d5c0994207030c862263e0297.camel@vmware.com> <20220224171538.jbf2cxzmhiwuinp4@jrouhaud> From: Peter Eisentraut In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 25.02.22 21:19, Jacob Champion wrote: > On Fri, 2022-02-25 at 16:28 +0000, Jacob Champion wrote: >> Ha, opr_sanity caught my use of cstring. I'll work on a fix later >> today. > > Fixed in v3. This patch contains no documentation. I'm having a hard time understanding what the name "session_authn_id" is supposed to convey. The comment for the Port.authn_id field says this is the "system username", which sounds like a clearer terminology.