<div dir="ltr">If you put PostGIS in its own schema, you just need to add that schema to the search path.<div><br></div><div>SET search_path = schema1, schema2, postgis, public;</div><div><br></div><div>I find that using a separate schema for PostGIS maximizes the separation between "system" code/data and "my" code/data.</div>
<div><br></div><div>-bborie</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jul 18, 2013 at 8:56 AM, Tim Keitt <span dir="ltr"><<a href="mailto:tkeitt@utexas.edu" target="_blank">tkeitt@utexas.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Does postgis have to be in public, or just the search path? I've not tried putting it into its own schema separate from the data (eg postgis in postgis schema, data in data schema). I've often thought that would be cleaner. I just have not tested it.<div>
<br></div><div>THK</div></div><div class="gmail_extra"><div><div class="h5"><br><br><div class="gmail_quote">On Wed, Jul 17, 2013 at 3:16 PM, Bborie Park <span dir="ltr"><<a href="mailto:dustymugs@gmail.com" target="_blank">dustymugs@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Rick,<div><br></div><div>First thing, upgrade your PostgreSQL servers to 9.2.4 due to the security fixes. Then install PostGIS using the CREATE EXTENSION approach into a separate schema on each database to be spatially-enabled.</div>
<div><br></div><div>-bborie</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jul 17, 2013 at 6:22 AM, <span dir="ltr"><<a href="mailto:Rick_Higginbotham@unigroupinc.com" target="_blank">Rick_Higginbotham@unigroupinc.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><font face="sans-serif">Hello All,</font>
<br>
<br><font face="sans-serif">We are embarking down the open source
software stack road and we are looking to get off on the right foot with
PostGIS so I thought the best place to start would be to ask the list a
question. We are currently running Postgres 9.2.2 on RHEL 6.3. We
have already created 5 pairs (master/standby streaming) of Postgres database
cluster to support the various business functions. We currently do
not have the PostGIS extension enabled on any of our existing databases.</font>
<br>
<br><font face="sans-serif">My best practices questions involve
our existing suite of Postgres database clusters. What are the best
practice recommendations for enabling geo spatial features on existing
Postgres databases? Should we build new Postgres database cluster
servers, enable PostGIS on the new database clusters and extract and load
into the new environment for the existing databases that we what to geo
spatial enable or geo spatial our existing database by creating the PostGIS
extension on the existing database clusters? </font>
<br>
<br><font face="sans-serif">Are there cons to installing PostGIS
and enabling the geospacial extensions on a system with 5 schema's where
only 1 schema has a geospacial requirement??</font>
<br>
<br><font face="sans-serif">Thanks for everyone's input and please
let me know if you need any more details.</font>
<br><font face="sans-serif"><br>
-Rick Higginbotham</font>
<pre>########################################################################
The information contained in this message, and any attachments thereto,
is intended solely for the use of the addressee(s) and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination, copying, or other use of the transmitted information is
prohibited. If you received this in error, please contact the sender
and delete the material from any computer. <a href="http://UNIGROUPINC.COM" target="_blank">UNIGROUPINC.COM</a>
########################################################################
</pre><br>_______________________________________________<br>
postgis-users mailing list<br>
<a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users" target="_blank">http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________<br>
postgis-users mailing list<br>
<a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users" target="_blank">http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div></div></div><span class="HOEnZb"><font color="#888888">-- <br><div dir="ltr"><a href="http://www.keittlab.org/" target="_blank">http://www.keittlab.org/</a></div>
</font></span></div>
<br>_______________________________________________<br>
postgis-users mailing list<br>
<a href="mailto:postgis-users@lists.osgeo.org">postgis-users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users" target="_blank">http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users</a><br>
<br></blockquote></div><br></div>