From: | Harald Fuchs <hari(dot)fuchs(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: hstore installed in a separate schema |
Date: | 2011-08-04 15:18:03 |
Message-ID: | 86k4atrys4.fsf@mgm.protecting.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Igor Neyman | 2011-08-04 18:58:10 | Re: query to get the list of key (reserverd) words? |
Previous Message | Bill Moran | 2011-08-04 14:30:29 | Re: query to get the list of key (reserverd) words? |