From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
---|---|
To: | Shinya11(dot)Kato(at)oss(dot)nttdata(dot)com |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Add --{no-,}bypassrls flags to createuser |
Date: | 2022-04-13 06:46:25 |
Message-ID: | 20220413.154625.2001259434473326066.horikyota.ntt@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
At Wed, 13 Apr 2022 14:51:35 +0900, Shinya Kato <Shinya11(dot)Kato(at)oss(dot)nttdata(dot)com> wrote in
> Hi,
>
> Add --{no-,}bypassrls flags to createuser.
> The following is an example of execution.
> --
> $ createuser a --bypassrls
> $ psql -c "\du a"
> List of roles
> Role name | Attributes | Member of
> -----------+------------+-----------
> a | Bypass RLS | {}
>
> --
>
> Do you think?
It is sensible to rig createuser command with full capability of
CREATE ROLE is reasonable.
Only --replication is added by commit 9b8aff8c19 (2010) since
8ae0d476a9 (2005). BYPASSRLS and NOBYPASSRLS were introduced by
491c029dbc (2014) but it seems to have forgotten to add the
corresponding createuser options.
By a quick search, found a few other CREATE ROLE optinos that are not
supported by createuser.
VALID UNTIL
ROLE (IN ROLE is -g/--role)
ADMIN
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2022-04-13 06:50:15 | Re: CLUSTER on partitioned index |
Previous Message | Antonin Houska | 2022-04-13 06:30:28 | Re: Temporary file access API |