Re: FWD: Re: Updated backslash consistency patch

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Greg Sabino Mullane <greg(at)turnstep(dot)com>
Subject: Re: FWD: Re: Updated backslash consistency patch
Date: 2009-02-07 21:38:06
Message-ID: 200902072138.n17Lc6W12069@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Stephen Frost wrote:
-- Start of PGP signed section.
> Bruce, et al,
>
> * Bruce Momjian (bruce(at)momjian(dot)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'?

\du/\dg shows the "Cannot login" specification, which I think is
sufficient.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2009-02-07 21:48:08 Re: Is a plan for lmza commpression in pg_dump
Previous Message David E. Wheeler 2009-02-07 21:35:07 Re: LIMIT NULL