<br><br><div class="gmail_quote">On Tue, Nov 24, 2009 at 5:01 PM, P Kishor <span dir="ltr"><<a href="mailto:punk.kish@gmail.com">punk.kish@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="h5">On Tue, Nov 24, 2009 at 3:55 PM, P Kishor <<a href="mailto:punk.kish@gmail.com">punk.kish@gmail.com</a>> wrote:<br>
> On Tue, Nov 24, 2009 at 2:56 PM, MarkW <<a href="mailto:mark.wimer@gmail.com">mark.wimer@gmail.com</a>> wrote:<br>
>><br>
>> On Tue, Nov 24, 2009 at 3:13 PM, P Kishor <<a href="mailto:punk.kish@gmail.com">punk.kish@gmail.com</a>> wrote:<br>
>>><br>
>>> Leo,<br>
>>><br>
>>> Many thanks for your clear replies. One follow-up question --<br>
>>><br>
>>> On Tue, Nov 24, 2009 at 1:29 PM, Paragon Corporation <<a href="mailto:lr@pcorp.us">lr@pcorp.us</a>> wrote:<br>
>>> ..<br>
>>> > --<br>
>>> > d. The notes above refer to setting the search_path and the<br>
>>> > session_path.<br>
>>> > Where is that done?<br>
>>> ><br>
>>> > You can do it in postgresql.conf or at the database level. The database<br>
>>> > level is better I think<br>
>>> ><br>
>>> > ALTER DATABASE mydb SET search_path = public, shared<br>
>>> ><br>
>>> ><br>
>>> > The above will have it set for good, except if you restore a db, you<br>
>>> > need to<br>
>>> > remember to rerun the above command.<br>
>>> ><br>
>>><br>
>>><br>
>>> In the above note, should I be setting the search_path to the<br>
>>> different project schemas as well, and not just 'public' and 'shared'?<br>
>>> So, if I have the following schemas in mydb, 'public', 'shared',<br>
>>> 'project1', 'project2' then the above command really should be<br>
>>><br>
>>> ALTER DATABASE mydb SET search_path = public, shared, project1, project2;<br>
>>><br>
>>> And, if I add another schema, 'project3', a few months later, then I run<br>
>>><br>
>>> ALTER DATABASE mydb SET search_path = public, shared, project1,<br>
>>> project2, project3;<br>
>>><br>
>>> Correct?<br>
>>><br>
>>> By the way, what is that search_path doing? What is it for? And, why<br>
>>> don't I have to set it if I have only a 'public' schema? Is that<br>
>>> because by default, a public schema doesn't need an explicit search<br>
>>> path?<br>
>>><br>
>>> Puneet.<br>
>>><br>
>><br>
>> If I could add another question to this thread since it's related to the<br>
>> PostGIS schema. I am moving to this "Project1" schema approach in prep for<br>
>> an upgrade and to keep the data in separate schema in the future. If my<br>
>> Project1 schema is dumped/backed up, then put back/restored after an upgrade<br>
>> of PostgreSQL/PostGIS, what's the best way to restore information in the<br>
>> Geometry_Columns table; should that be saved, or should I be using a<br>
>> function to re-populate the Geometry_Columns table?<br>
>><br>
><br>
> I am not sure what you are asking above. If you backup Project1<br>
> schema, then restore it in another db, the_geom columns will all come<br>
> back. After all, backup will back up all the tables in that schema,<br>
> and restore will restore them. A table is a table, doesn't matter what<br>
> kind of columns it holds.<br>
><br>
> Maybe I misunderstood your concern.<br>
><br>
><br>
><br>
<br>
<br>
</div></div>Yeah, I am pretty sure I misunderstood your problem. Disregard my<br>
response, and let's wait for a more educated response. I am curious as<br>
well now.<br>
<br>
<div><div></div><div class="h5">> Puneet Kishor <a href="http://www.punkish.org" target="_blank">http://www.punkish.org</a><br>
> Carbon Model <a href="http://carbonmodel.org" target="_blank">http://carbonmodel.org</a><br>
> Charter Member, Open Source Geospatial Foundation <a href="http://www.osgeo.org" target="_blank">http://www.osgeo.org</a><br>
> Science Commons Fellow, <a href="http://sciencecommons.org/about/whoweare/kishor" target="_blank">http://sciencecommons.org/about/whoweare/kishor</a><br>
> Nelson Institute, UW-Madison <a href="http://www.nelson.wisc.edu" target="_blank">http://www.nelson.wisc.edu</a><br>
> -----------------------------------------------------------------------<br>
> Assertions are politics; backing up assertions with evidence is science<br>
> =======================================================================<br>
> Sent from Madison, Wisconsin, United States<br></div></div></blockquote><div><br>Thanks Puneet - sorry for the confusion. I was referring to the
"geometry_columns" table - I believe it's always in the public schema
along with postGIS functions and not in each schema; I wonder if I need
to worry about backing that up, or is this what one of the newer
functions is for:<br>
<a href="http://postgis.refractions.net/documentation/manual-1.4/Populate_Geometry_Columns.html">http://postgis.refractions.net/documentation/manual-1.4/Populate_Geometry_Columns.html</a><br><br>Mark<br> </div></div><br>