Re: Add --{no-,}bypassrls flags to createuser

Przemysław Sztoch <przemyslaw@sztoch.pl>

From: Przemysław Sztoch <przemyslaw@sztoch.pl>
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: Shinya Kato <Shinya11.Kato@oss.nttdata.com>, Nathan Bossart <nathandbossart@gmail.com>, Robert Haas <robertmhaas@gmail.com>, Michael Paquier <michael@paquier.xyz>, Kyotaro Horiguchi <horikyota.ntt@gmail.com>, Daniel Gustafsson <daniel@yesql.se>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2022-05-22T07:55:37Z
Lists: pgsql-hackers
David G. Johnston wrote on 5/19/2022 3:46 AM:
> I think that this feature is at least worth considering - but absent 
> an existing command that does this I would agree that doing so 
> constitutes a separate feature.
>
> As an aside, I'd rather overcome this particular objection by having 
> the CREATE object command all accept an optional "COMMENT IS" clause.
>
> David J.
The createuser command is typically used by IT personnel unfamiliar with 
SQL and unfamiliar with psql.
They often use this command because software installation procedures 
require it.
Lack of comment then causes more mess in the configuration of larger 
servers.
I still think it's worth adding the --comment argument to execute the 
next SQL statement by createuser.
This will simplify the setup scripts and installation instructions for 
the final software.

I believe that it is not worth dividing it into a separate program.

The same --comment argument is needed for the createdb command.
-- 
Przemysław Sztoch | Mobile +48 509 99 00 66

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Fix output of createuser --help with --valid-until

  2. createuser: Add support for more clause types through new options

  3. createuser: Cleanup and fix internal option ordering

  4. Add REPLICATION privilege for ROLEs