Re: Add --{no-,}bypassrls flags to createuser
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>, Shinya Kato <Shinya11.Kato@oss.nttdata.com>, Daniel Gustafsson <daniel@yesql.se>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2022-04-21T04:29:57Z
Lists: pgsql-hackers
On Tue, Apr 19, 2022 at 12:13:51PM -0400, Robert Haas wrote: > On Mon, Apr 18, 2022 at 9:50 PM Kyotaro Horiguchi > <horikyota.ntt@gmail.com> wrote: >> 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.. > > Hmm, yeah, I hadn't quite realized what the problem was when I wrote > that. I honestly don't know what to do about that. Renaming the > existing option is not great, but having the syntax diverge between > SQL and CLI is not great either. Giving up is also not great. Not sure > what is best. Changing one existing option to mean something entirely different should be avoided, as this could lead to silent breakages. As the origin of the problem is that the option --role means "IN ROLE" in the SQL grammar, we could keep around --role for compatibility while marking it deprecated, and add two new options whose names would be more consistent with each other. One choice could be --role-name and --in-role-name, where --in-role-name maps to the older --role, just to give an idea. -- Michael
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix output of createuser --help with --valid-until
- 4ca998595788 16.0 landed
-
createuser: Add support for more clause types through new options
- 08951a7c93cf 16.0 landed
-
createuser: Cleanup and fix internal option ordering
- 50e4c280f066 16.0 landed
-
Add REPLICATION privilege for ROLEs
- 9b8aff8c192e 9.1.0 cited