Re: hstore installed in a separate schema

Thank you Harald

--- On Thu, 8/4/11, Harald Fuchs <hari(dot)fuchs(at)gmail(dot)com> wrote:

> From: Harald Fuchs <hari(dot)fuchs(at)gmail(dot)com>
> Subject: Re: [GENERAL] hstore installed in a separate schema
> To: pgsql-general(at)postgresql(dot)org
> Received: Thursday, August 4, 2011, 11:18 AM
> In article <1312401318(dot)5199(dot)YahooMailClassic(at)web120108(dot)mail(dot)ne1(dot)yahoo(dot)com>,
> Ioana Danes <ioanasoftware(at)yahoo(dot)ca>
> writes:
>
> > Hi,
> > I am planning to use the contrib module hstore
> > but I would like to install it on a separate schema,
> not public,
> > and include the schema in the search_path.
> > Do you know if there are any issues with this
> scenario.
> > In the hstore.sql script I see it forces it into
> public:
>
> > -- Adjust this setting to control where the objects
> get created.
> > SET search_path = public;
>
> > I did some tests for my use cases and it all works
> fine...
>
> That's the way I use any contrib module because it doesn't
> mix my own
> stuff with the module's stuff.  With an
>
>   ALTER DATABASE mydb SET search_path = public,
> hstore
>
> all that works transparently.
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>