Re: fixing CREATEROLE

From: walther(at)technowledgy(dot)de
To: Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>
Cc: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: fixing CREATEROLE
Date: 2022-11-29 07:05:46
Message-ID: 180417a8-5ab2-30aa-fb7a-b753c1e85dc1@technowledgy.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Mark Dilger:
>> Isn't this just GRANT .. WITH SET FALSE, INHERIT FALSE, ADMIN TRUE? That should allow role administration, without actually granting membership in that role, yet, right?
>
> Can you clarify what you mean here? Are you inventing a new syntax?
>
> +GRANT bob TO alice WITH SET FALSE, INHERIT FALSE, ADMIN TRUE;
> +ERROR: syntax error at or near "SET"
> +LINE 1: GRANT bob TO alice WITH SET FALSE, INHERIT FALSE, ADMIN TRUE...

This is valid syntax on latest master.

Best,

Wolfgang

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2022-11-29 07:08:27 Re: Add LZ4 compression in pg_dump
Previous Message houzj.fnst@fujitsu.com 2022-11-29 06:53:44 RE: Avoid streaming the transaction which are skipped (in corner cases)