| From: | Pavel Luzanov <p(dot)luzanov(at)postgrespro(dot)ru> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | David Zhang <david(dot)zhang(at)highgo(dot)ca>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: psql: Add role's membership options to the \du+ command |
| Date: | 2023-03-21 03:37:22 |
| Message-ID: | d1779a39-bc47-f7f2-6ab6-8d37bf4529b1@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>>> I would suggest tweaking the test output to include regress_du_admin ...
I found (with a help of cfbot) difficulty with this. The problem is the bootstrap superuser name (oid=10).
This name depends on the OS username. In my case it's pal, but in most cases it's postgres or something else.
And the output of \du regress_du_admin can't be predicted:
\du regress_du_admin
List of roles
Role name | Attributes | Member of
------------------+-------------+-------------------------------------
regress_du_admin | Create role | regress_du_role0 from pal (a, i, s)+
| | regress_du_role1 from pal (a, i, s)+
| | regress_du_role2 from pal (a, i, s)
So, I decided not to include regress_du_admin in the test output.
Please, see version 5 attached. Only tests changed.
-----
Pavel Luzanov
| Attachment | Content-Type | Size |
|---|---|---|
| v5-0001-psql-show-membership-options-in-the-du-command.patch | text/x-patch | 13.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2023-03-21 05:03:24 | Re: Eliminating SPI from RI triggers - take 2 |
| Previous Message | Andres Freund | 2023-03-21 02:34:51 | Re: Track IO times in pg_stat_io |