| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Brendan Jurd" <direvus(at)gmail(dot)com> |
| Cc: | "Chris Browne" <cbbrowne(at)acm(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: psql show dbsize? |
| Date: | 2007-11-01 03:33:46 |
| Message-ID: | 25858.1193888026@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Kirkwood | 2007-11-01 08:19:24 | Cache lookup failed for relation X [was: DROP FUNCTION cache lookup failed for relation X] |
| Previous Message | Brendan Jurd | 2007-11-01 03:12:18 | Re: psql show dbsize? |