| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Justin Camp <j(at)intuitivecreations(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: limiting \l [list all databases] |
| Date: | 2004-03-23 18:09:04 |
| Message-ID: | 200403231809.i2NI94p24603@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Justin Camp wrote:
> Greetings!
>
> I apologize if this has been previously posted..
>
> I run a server with multiple clients running databases on one server,
> and I was wondering if there was a way to limit the list all databases
> function within the pgsql program to only list databases within a
> criteria, say, what they have permission to see?
>
> Or perhaps, if that is not possible, a way to shut off the
> functionality entirely, from the server side?
It is not possible. pg_database is a global table, visible to all
databases. I can't think of a way to limit such visibility. Perhaps
you can create a pg_database in the public schema and have it only
return the current database and template1. That might work, or it might
not, but the pg_database will still be visible in pg_catalog.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Subbiah, Stalin | 2004-03-23 18:16:52 | Re: Databases Vs. Schemas |
| Previous Message | Bruno Wolff III | 2004-03-23 17:59:43 | Re: Testing for existence of a record before insert |