Re: FWD: Re: Updated backslash consistency patch - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: FWD: Re: Updated backslash consistency patch
Date
Msg-id 20090122023226.GF32428@tamriel.snowman.net
Whole thread Raw
In response to Re: FWD: Re: Updated backslash consistency patch  (Bruce Momjian <bruce@momjian.us>)
Responses Re: FWD: Re: Updated backslash consistency patch  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: FWD: Re: Updated backslash consistency patch  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
Bruce, et al,

* Bruce Momjian (bruce@momjian.us) wrote:
>       \dg      [PATTERN]    list roles (groups)
>       \du      [PATTERN]    list roles (users)

Seeing this list reminded me of a pet-peeve..  \du and \dg actually show
the same info, that's fine, but neither of them show the rolcanlogin
value.  As someone who has a bad habit of doing 'create role blah;' for
new users this can get very annoying.  I also have people complain to me
that they can't figure out why a new user can't log in after they did
the same thing.  Could we get that changed?  Or maybe have 'connections'
say something different when you don't have rolcanlogin besides 'no
limit'?

>       \dp      [PATTERN]    list table, view, and sequence access privileges

erp, I don't think I changed this in my column-level privleges patch..
Should we explicitly mention column in this list?
Thanks,
    Stephen

pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: FWD: Re: Updated backslash consistency patch
Next
From: Andrew Dunstan
Date:
Subject: parallel restore