Re: privileges oddity

From: Scott Ribe <scott_ribe(at)elevated-dev(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: privileges oddity
Date: 2020-08-07 20:29:29
Message-ID: A7BB8B16-C2AD-47BC-BF78-CAACE6841C4A@elevated-dev.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

So, one last follow-up, perhaps \du or \du+ should show when a role is mapped that way. If I'd seen a clue to this setting that had been made "before I got here" it would have been figured out sooner.

I realize ALTER ROLE... SET... can be used to set many more defaults, and there could be some debate about how much to display with \du[+], but the fact that a role abandons all its privs and adopts a different set seems like pretty important info to surface ;-)

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2020-08-07 20:38:31 Re: privileges oddity
Previous Message Scott Ribe 2020-08-07 19:51:34 Re: privileges oddity