| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Joe Conway (wwc)" <jconway(at)cox(dot)net> |
| Cc: | Zeugswetter Andreas SB SD <ZeugswetterA(at)spardat(dot)at>, Fernando Nasser <fnasser(at)redhat(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: RFD: schemas and different kinds of Postgres objects |
| Date: | 2002-01-23 17:00:56 |
| Message-ID: | 3326.1011805256@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Joe Conway (wwc)" <jconway(at)cox(dot)net> writes:
> I think it would be desirable to be able to restrict users from
> "publishing" objects into the public schema.
Sure. I'm envisioning that namespaces will have ACLs --- that's what
will keep private namespaces private. So, while public would by default
be world-writable (at least in the backwards-compatibility case),
there'd be nothing stopping you from marking it as read-only to some
users.
Come to think of it, that's still another reason not to have an "any"
wildcard: there's no way to put any restrictions on what appears in
such a namespace.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brent Verner | 2002-01-23 17:01:50 | Re: pltcl build problem on FreeBSD (was: Re: pltlc and pltlcu problems) |
| Previous Message | Joe Conway (wwc) | 2002-01-23 16:56:15 | Re: RFD: schemas and different kinds of Postgres objects |