Skip site navigation (1) Skip section navigation (2)

Re: Modifying and solidifying contrib

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Bruce Momjian <bruce(at)momjian(dot)us>
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:44:44
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Bruce Momjian wrote:
> 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.

This suggests maybe we need to look at beefing up a few things. For 
example, an alias facility that provided a name in schema X for things 
in schema Y would help lots here. (You want everything visible? Just 
alias it in public.) ISTR such things in DB2, although it's now many 
years since I laid hands on it, so my memory could well be very faulty.

Also, ability to append to the search path rather than just set it could 
help, as might ability to add names of non-existent schemas (which would 
be ignored at run time when found not to exist).



In response to


pgsql-hackers by date

Next:From: Bruce MomjianDate: 2007-01-29 21:46:27
Subject: Re: Modifying and solidifying contrib
Previous:From: Bruce MomjianDate: 2007-01-29 21:32:43
Subject: Re: Modifying and solidifying contrib

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group