| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Shinya Kato <Shinya11(dot)Kato(at)oss(dot)nttdata(dot)com> |
| Cc: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add --{no-,}bypassrls flags to createuser |
| Date: | 2022-04-14 09:57:31 |
| Message-ID: | 25D72E41-9ED2-4EED-B18E-E7979E031DDB@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 14 Apr 2022, at 09:42, Shinya Kato <Shinya11(dot)Kato(at)oss(dot)nttdata(dot)com> wrote:
> To add the ROLE clause, the originally existing --role option (corresponding to the IN ROLE clause) is changed to the --in-role option. Would this not be good from a backward compatibility standpoint?
- printf(_(" -g, --role=ROLE new role will be a member of this role\n"));
+ printf(_(" -g, --in-role=ROLE new role will be a member of this role\n"));
+ printf(_(" -G, --role=ROLE this role will be a member of new role\n"));
Won't this make existing scripts to behave differently after an upgrade? That
seems like something we should avoid at all costs.
--
Daniel Gustafsson https://vmware.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alena Katkova | 2022-04-14 11:36:38 | GSoC: New and improved website for pgjdbc (JDBC) (2022) |
| Previous Message | wangw.fnst@fujitsu.com | 2022-04-14 09:33:15 | RE: Skipping schema changes in publication |