| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | David Fetter <david(at)fetter(dot)org>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Glaesemann <grzm(at)seespotcode(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Modifying and solidifying contrib |
| Date: | 2007-01-29 21:32:43 |
| Message-ID: | 200701292132.l0TLWh603258@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan wrote:
> Bruce Momjian wrote:
> > Keep in mind all contrib loads into public, and I don't remember any
> > namespace conflict issues in the past.
> >
>
> That is beside the point. Of course there haven't been conflicts -
> precisely because a single group controls the whole lot. What I said was
> that we should behave as sane third party extension authors would,
> namely to use their own namespace to protect themselves from conflicts
> with other unknown extensions. It's called setting a good example or
> eating your own dog food.
The problem I see controlling per-user search_path if +10 extensions are
instlalled, and you want them always to be available by default.
Also, are we going to use per-schema permissions so that the schemas are
not visible by default? That _might_ allow us to install more by
default.
--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2007-01-29 21:44:44 | Re: Modifying and solidifying contrib |
| Previous Message | Andrew Dunstan | 2007-01-29 21:29:35 | Re: Modifying and solidifying contrib |