Andrea, In theory you can but you shouldn't. It would get very confusing and you would quickly loose your sanity as you would have to schema qualify each postgis function, geometry type etc and it wouldn't work with any third party tools correctly because they most likely will not schema qualify. I would avoid it. You can as of PostGIS 1.4 (well technicall 1.3 since the names of the .so, .dell changed) have databases running postgis 1.3, another running postgis 1.4 and yet another running trunk postgis 1.5 If you need different versions of postgis -- you would be better off installing them in different databases. We for example have a template_postgis15 a template_postgis14 and a template_postgis13 and when we want to use PostGIS 1.5 we create a new database using the template_postgis15 as the template -- take the backup of my old postgis database (say from 1.3 or 1.4) (minus the public schema) and then restore on this fresh postgis 1.5 db. Seems to work pretty well (even works if you do restore the public schema though will give errors you can ignore as well since all the functions in your backup that are already installed will be ignored). If you want to create a backup file minus the public schema -- you can use the pg_dump -N public option to backup all schemas except public. Hope that helps, Regina
_____ From: [email protected] [mailto:[email protected]] On Behalf Of Andrea Peri Sent: Sunday, October 04, 2009 5:22 PM To: [email protected] Subject: Re: [postgis-users] Install postgis on a different schema Hi, I'm testing the Stephen's approach. It work very well. In effect with this solution it work very well . Hovewer I'll try even to install postgis on different schema. I like to know if is possible to install some version of postgis on different schemas of the same database. This knowledge can be useful when I need to backup and restore a single schema even if the principal version of postgis is changed. Many thx for hints. Andrea. >Generally speaking I tend to follow >Stephen's approach because the installing postgis in a non-public schema is >not as tried and tested. >I'm not even sure if there are any assumptions embedded in products that >support postgis we don't know that assume postgis is in public. > >Aside from that -- there isn't any problem with that as long as you add the >postgis schema to your database search_path. > >Hope that helps, >Regina -- ----------------- Andrea Peri . . . . . . . . . qwerty àèìòù -----------------
_______________________________________________ postgis-users mailing list [email protected] http://postgis.refractions.net/mailman/listinfo/postgis-users
