Re: Allow CURRENT_ROLE in GRANTED BY - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Allow CURRENT_ROLE in GRANTED BY
Date
Msg-id b720a227-3df7-c23e-79e7-61a89eade34e@2ndquadrant.com
Whole thread Raw
In response to Re: Allow CURRENT_ROLE in GRANTED BY  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: Allow CURRENT_ROLE in GRANTED BY  (Daniel Gustafsson <daniel@yesql.se>)
List pgsql-hackers
On 2020-12-30 13:43, Simon Riggs wrote:
> On Thu, 10 Dec 2020 at 18:40, Peter Eisentraut
> <peter.eisentraut@2ndquadrant.com> wrote:
>>
>> On 2020-06-24 20:21, Peter Eisentraut wrote:
>>> 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.
>>
>> Here is the highly anticipated and quite underwhelming second part of
>> this patch set.
> 
> Looks great, but no test to confirm it works. I would suggest adding a
> test and committing directly since I don't see any cause for further
> discussion.

Committed with some tests.  Thanks.

-- 
Peter Eisentraut
2ndQuadrant, an EDB company
https://www.2ndquadrant.com/



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: [PATCH] pg_hba.conf error messages for logical replication connections
Next
From: Peter Eisentraut
Date:
Subject: Re: SELECT INTO deprecation