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 1joA1h-0005U2-Mk for pgsql-hackers@arkaria.postgresql.org; Wed, 24 Jun 2020 18:21:37 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1joA1g-00064K-J3 for pgsql-hackers@arkaria.postgresql.org; Wed, 24 Jun 2020 18:21:36 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1joA1g-00064D-Bf for pgsql-hackers@lists.postgresql.org; Wed, 24 Jun 2020 18:21:36 +0000 Received: from forward5-smtp.messagingengine.com ([66.111.4.239]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1joA1e-0001t3-4P for pgsql-hackers@postgresql.org; Wed, 24 Jun 2020 18:21:35 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailforward.nyi.internal (Postfix) with ESMTP id 26E6D194060F; Wed, 24 Jun 2020 14:21:32 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 24 Jun 2020 14:21:32 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=Ibuvd+q39c4LdeFOYMwhSvLtPuzILSU1Gpg1gPSCY Ro=; b=NKIEFwOInSixij7Nfe77ZVcags3jm6gvO5hGtS3Ut/rhPJ0VMlwrbzq8b L+Sz0EHwGKo+Ngq7qx23UhDJMKBCR8SSvqS1duibvM592MatryAUb89MDn6cQ+h4 5kzqpRHhgjwdLcWoJMOu+m7LWXxGuuyx9uMw6SEJXS/Xkn4tGFY7FxUSm2AU+N8m oxug2qxv8xcd7E9xz1K+nTbgn4Hd3MvlSI9ydbjJ/D3FsU1lL+G5KDUCiXNTRCX3 dINCEsvS7wHnn1mWA8xtOkxS4bDA8RqCFIYGj+H1T03E4PpiNz9KCRPwluce4Te3 3zfUqSFpEzObXlACQfNjiOBUn4H3A== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrudekjedguddukecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhohfkffgfgggjtgfgse htkeertddtfeejnecuhfhrohhmpefrvghtvghrucfgihhsvghnthhrrghuthcuoehpvght vghrrdgvihhsvghnthhrrghuthesvdhnughquhgrughrrghnthdrtghomheqnecuggftrf grthhtvghrnhepleffffetffejfefhheffveekieetieekudeffffhheevieelhfethfeg feduhedtnecuffhomhgrihhnpedvnhguqhhurggurhgrnhhtrdgtohhmnecukfhppeelfe drvdegfedrudeluddrvdefkeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhep mhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvghnthhrrghuthesvdhnughquhgrughrrg hnthdrtghomh X-ME-Proxy: Received: from april.pezone.net (p5df3bfee.dip0.t-ipconnect.de [93.243.191.238]) by mail.messagingengine.com (Postfix) with ESMTPA id A9FA63280064; Wed, 24 Jun 2020 14:21:30 -0400 (EDT) Subject: Re: Allow CURRENT_ROLE in GRANTED BY To: Vik Fearing , pgsql-hackers References: From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: Date: Wed, 24 Jun 2020 20:21:29 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2020-06-24 10:12, Vik Fearing wrote: > On 6/24/20 8:35 AM, Peter Eisentraut wrote: >> I was checking some loose ends in SQL conformance, when I noticed: We >> support GRANT role ... GRANTED BY CURRENT_USER, but we don't support >> CURRENT_ROLE in that place, even though in PostgreSQL they are >> equivalent.  Here is a trivial patch to add that. > > > The only thing that isn't dead-obvious about this patch is the commit > message says "[PATCH 1/2]". What is in the other part? Hehe. The second patch is some in-progress work to add the GRANTED BY clause to the regular GRANT command. More on that perhaps at a later date. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services