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

From Stephen Frost
Subject Re: Updated backslash consistency patch
Date
Msg-id 20090201142118.GN8123@tamriel.snowman.net
Whole thread Raw
In response to Re: Updated backslash consistency patch  (David Fetter <david@fetter.org>)
Responses Re: Updated backslash consistency patch  (Grzegorz Jaskiewicz <gj@pointblue.com.pl>)
Re: Updated backslash consistency patch  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
* David Fetter (david@fetter.org) wrote:
> On Sun, Feb 01, 2009 at 04:54:08AM +0000, Grzegorz Jaskiewicz wrote:
> > On 23 Jan 2009, at 00:03, Tom Lane wrote:
> >> Stephen Frost <sfrost@snowman.net> writes:
> >>> 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.
> >>
> >> +1 for fixing that.
> >
> > was it that easy, or I got it wrong?
> >
> > :)
>
> I think Stephen meant that they should add a column to the output.
> Stephen?

It was, but that was before the output-as-table changes were done.  It
looks like when those were committed, 'Cannot login' was added as an
attribute.  Having 'Can login' (as this patch proposes) seems reasonable
to me.

On a side note, I have to say that I'm not exactly thrilled with the new
table-\du, especially since the List of roles isn't set up to break
across lines cleanly.

So if you have alot of roles granted, and even a couple attributes, it
gets ugly..
Stephen

pgsql-hackers by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: adding stuff to parser, question
Next
From: Grzegorz Jaskiewicz
Date:
Subject: Re: Updated backslash consistency patch