From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
---|---|
To: | robertmhaas(at)gmail(dot)com |
Cc: | Shinya11(dot)Kato(at)oss(dot)nttdata(dot)com, daniel(at)yesql(dot)se, michael(at)paquier(dot)xyz, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Add --{no-,}bypassrls flags to createuser |
Date: | 2022-04-19 01:50:12 |
Message-ID: | 20220419.105012.1677795152077894444.horikyota.ntt@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thanks!
At Mon, 18 Apr 2022 09:59:48 -0400, Robert Haas <robertmhaas(at)gmail(dot)com> wrote in
> On Fri, Apr 15, 2022 at 2:33 AM Kyotaro Horiguchi
> <horikyota(dot)ntt(at)gmail(dot)com> wrote:
> > > printf(_(" -b, --belongs-to=ROLE new role will be a member of this role\n"));
> >
> > + printf(_(" -m, --membership=ROLE this role will be a member of new role\n"));
> >
> > membership sounds somewhat obscure, it seems *to me* members is clearer
> >
> > > printf(_(" -m, --member=ROLE new role will be a member of this role\n"));
> >
> > I'd like to hear others' opinions.
>
> I think that we need to preserve consistency with the SQL syntax as
> much as possible -- and neither MEMBER nor MEMBERSHIP nor BELONGS_TO
> appear in that syntax. A lot of the terminology in this area seems
> poorly chosen and confusing to me, but having two ways to refer to
> something probably won't be an improvement even if the second name is
> better-chosen than the first one.
Hmm.. So, "-r/--role" and "-m/--member(ship)" is the (least worse) way
to go? Or we can give up adding -m for the reason of being hard to
name it..
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | wangw.fnst@fujitsu.com | 2022-04-19 01:52:15 | RE: Logical replication timeout problem |
Previous Message | Kyotaro Horiguchi | 2022-04-19 01:45:15 | Re: BufferAlloc: don't take two simultaneous locks |