Re: Final /contrib cleanup -- yes/no?

From: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Final /contrib cleanup -- yes/no?
Date: 2008-11-07 03:07:34
Message-ID: 200811062207.35651.xzilla@users.sourceforge.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thursday 06 November 2008 17:35:58 Josh Berkus wrote:
> Joshua D. Drake wrote:
> > On Thu, 2008-11-06 at 17:24 -0500, Tom Lane wrote:
> >> Josh Berkus <josh(at)agliodbs(dot)com> writes:
> >>> The way the SQL scripts currently work, there is no way to manage what
> >>> schema the contrib modules get built in *except* to edit the scripts.
> >>
> >> Right, that's the intended and documented way to do it.
> >
> > I believe the intention is a bad one. They should be installed per the
> > settings of the user installing them. Whether that be through an ALTER
> > ROLE/USER or PGOPTIONS.
>
> Eh, Tom has a point. If we build module loading for 8.5, we shouldn't
> change the functionality in the interim for 8.4. Annoying as it is.
>

Also be aware that some of those modules really do require being in the public
schema (which I have learned the hard way). It's probably possible to make
them work in different schemas, but just changing the install schema will
break them right now (i think intarray is an example of one)

--
Robert Treat
Conjecture: http://www.xzilla.net
Consulting: http://www.omniti.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message KaiGai Kohei 2008-11-07 03:13:08 Re: The suppress_redundant_updates_trigger() works incorrectly
Previous Message Greg Smith 2008-11-07 02:31:12 Re: [WIP] In-place upgrade