From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Brendan Jurd <direvus(at)gmail(dot)com>, Chris Browne <cbbrowne(at)acm(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: psql show dbsize? |
Date: | 2008-03-07 15:56:08 |
Message-ID: | 200803071556.m27Fu8w16685@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Added to TODO:
o Have \l+ show database size, if permissions allow
Ideally it will not generate an error for invalid permissions
---------------------------------------------------------------------------
Tom Lane wrote:
> "Brendan Jurd" <direvus(at)gmail(dot)com> writes:
> > I'd find this convenient too. Although \l+ would be more consistent
> > with the \d series of commands.
>
> Putting it into \l+ would address my gripe about increased execution
> time. The permissions angle still bothers me though. AFAIR there are
> no psql catalog-inquiry backslash commands that require any special
> permissions, so making \l+ into something that's quite likely to fail
> in a locked-down installation seems out of place.
>
> Is there a way to get it to just not print anything, instead of failing,
> for DBs you don't have privileges for?
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Teodor Sigaev | 2008-03-07 15:56:37 | Re: Behaviour of to_tsquery(stopwords only) |
Previous Message | Greg Smith | 2008-03-07 15:33:51 | Re: shared_buffers and shmmax what are the max recommended values? |