| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: allowing for control over SET ROLE |
| Date: | 2022-11-18 18:43:14 |
| Message-ID: | 20221118184314.e4z3n5wzpcif5r52@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2022-Nov-18, Robert Haas wrote:
> On Thu, Nov 17, 2022 at 7:24 PM Jeff Davis <pgsql(at)j-davis(dot)com> wrote:
> > But I'm fine if you'd like to move on with the SET ROLE privilege
> > instead, as long as we believe it grants a stable set of capabilities
> > (and conversely, that if the SET ROLE privilege is revoked, that it
> > revokes a stable set of capabilities).
>
> OK.
>
> Here's a rebased v3 to see what cfbot thinks.
I think this hunk in dumpRoleMembership() leaves an unwanted line
behind.
/*
- * Previous versions of PostgreSQL also did not have a grant-level
+ * Previous versions of PostgreSQL also did not have grant-level options.
* INHERIT option.
*/
(I was just looking at the doc part of this patch.)
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"El hombre nunca sabe de lo que es capaz hasta que lo intenta" (C. Dickens)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2022-11-18 18:43:16 | Re: allowing for control over SET ROLE |
| Previous Message | Thomas Munro | 2022-11-18 18:38:53 | Re: Collation version tracking for macOS |