From: | Przemysław Sztoch <przemyslaw(at)sztoch(dot)pl> |
---|---|
To: | Shinya Kato <Shinya11(dot)Kato(at)oss(dot)nttdata(dot)com> |
Cc: | Nathan Bossart <nathandbossart(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Re: Add --{no-,}bypassrls flags to createuser |
Date: | 2022-05-05 22:08:22 |
Message-ID: | a720383d-9bf2-fcb7-22fa-aeea114c86a5@sztoch.pl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Dear Shinya,
Too bad there's no --comment parameter to do COMMENT ON ROLE name IS
'Comment';
As you already make such changes in createuser, I would like to ask for
an additional --comment parameter
that will allow sysadmins to set a comment with additional information
about the new DB user.
psql is scary for some. :-)
Overall a very useful patch. I needed bypassrls several times recently.
Shinya Kato wrote on 4/28/2022 8:06 AM:
> Thank you for the reviews!
>
> On 2022-04-26 05:19, Nathan Bossart wrote:
>
>> - printf(_(" -g, --role=ROLE new role will be a member
>> of this role\n"));
>> + printf(_(" -g, --role=ROLE new role will be a member of
>> this role\n"));
>> This looks lik an unexpected change.
>
> I fixed it.
>
>
>>> I'm ok with -m/--member as well (like with --role only one role can be
>>> specified per switch instance so member, not membership, the later
>>> meaning,
>>> at least for me, the collective).
>>>
>>> That -m doesn't match --role-to is no worse than -g not matching
>>> --role, a
>>> short option seems worthwhile, and the -m (membership) mnemonic
>>> should be
>>> simple to pick-up.
>>>
>>> I don't see the addition of "-name" to the option name being
>>> beneficial.
>>>
>>> Yes, the standard doesn't use the "TO" prefix for "ROLE" - but
>>> taking that
>>> liberty for consistency here is very appealing and there isn't
>>> another SQL
>>> clause that it would be confused with.
>>
>> +1 for "member". It might not be perfect, but IMO it's the clearest
>> option.
>
> Thanks! I changed the option "--membership" to "--member".
>
>
> For now, I also think "-m / --member" is the best choice, although it
> is ambiguous:(
> I'd like to hear others' opinions.
>
> regards
>
>
> --
> Shinya Kato
> Advanced Computing Technology Center
> Research and Development Headquarters
> NTT DATA CORPORATION
--
Przemysław Sztoch | Mobile +48 509 99 00 66
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-05-05 22:29:23 | First-draft release notes for next week's minor releases |
Previous Message | Przemysław Sztoch | 2022-05-05 19:44:15 | Re: [PATCH] Completed unaccent dictionary with many missing characters |