From: | "Brendan Jurd" <direvus(at)gmail(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Bernd Helmle" <mailings(at)oopsware(dot)de>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Show INHERIT in \du |
Date: | 2008-02-15 00:09:44 |
Message-ID: | 37ed240d0802141609j74d0ef47p4ec60a84ae68605a@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On Fri, Feb 15, 2008 at 10:50 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Brendan Jurd" <direvus(at)gmail(dot)com> writes:
> > What about connection limit? I suppose we could combine it into the
> > privileges column, and refrain from displaying anything for "no
> > limit".
>
> "5 connections" seems a bit odd for a "privilege". I'd be happy with
> leaving that as a separate column. Or I guess we could choose a
> less specific word (like "attributes"?) for the column heading.
>
"Attributes" works better IMO. The manual refers to INHERIT and LOGIN
as "attributes" rather than "privileges", so I would go for
"attributes" regardless of where we place connection limit.
Leaving connection limit in a separate column would be okay, but if
most installations seldom use connection limit (and I suspect this is
true), that's a chunky amount of underutilised space in the \du
output.
Cheers
BJ
From | Date | Subject | |
---|---|---|---|
Next Message | Decibel! | 2008-02-15 01:12:47 | Re: wishlist for 8.4 |
Previous Message | Tom Lane | 2008-02-14 23:50:46 | Re: Show INHERIT in \du |
From | Date | Subject | |
---|---|---|---|
Next Message | Phoenix Kiula | 2008-02-15 00:10:36 | Re: PG quitting sporadically!! |
Previous Message | Tom Lane | 2008-02-14 23:50:46 | Re: Show INHERIT in \du |