Oops. My bad. I had a typo on the page. I'll fix. That should have read January 7, 2012. If you are using that one, then you should be good to go since I haven't released a new version yet. Just use the 9.1 binaries on that page and restore your backup and you should be good to go.
_____ From: [email protected] [mailto:[email protected]] On Behalf Of John Callahan Sent: Wednesday, January 25, 2012 11:50 PM To: PostGIS Users Discussion Subject: Re: [postgis-users] migration/upgrade advice Thanks Regina. The version I'm running was downloaded last August from http://www.postgis.org/download/windows/experimental.php, which mentions Jan 7 on that page. "SELECT PostGIS_Full_Version();" returns "POSTGIS="2.0.0SVN" GEOS="3.3.0-CAPI-1.7.0" PROJ="Rel. 4.6.1, 21 August 2008" LIBXML="2.7.6" USE_STATS" Where is the best location to get the latest postgis? checkout via SVN? I will give the hard upgrade method a try. - John *********************************************** John Callahan, Research Scientist Delaware Geological Survey, University of Delaware URL: http://www.dgs.udel.edu ************************************************* On Wed, Jan 25, 2012 at 5:40 PM, Paragon Corporation <[email protected]> wrote: > I unfortunately have to move my Postgres/PostGIS database to a new Windows server. My current (source) db is Postgres 9.0.2 with PostGIS 2.0.0SVN (I believe from Jan 2011.) January 2011 is a bit old or do you mean 2012? > The new (destination) db will likely be Postgres 9.1.2. It seems like I can use pg_dump to go from 9.0.2 to 9.1.2, as long as I use the 9.1 version of pg_dump. Is that true? Correct -- I do it alll tthe time. > For PostGIS 2.0, I plan to install the same version on both the source and destination db. I'll do this before importing from pg_dump. I can then update PostGIS on the new db after the migration is complete. Does that make sense? or should I install a newer version of PostGIS immediately? Depends how old your version is -- if its really 2011, I'm not sure our upgrade script can handle that far back cleanly. You can try. I think your safest bet though is to: 1) Install the newest version of binaries on PostgreSQL 9.1 2) Create a new db with the latest PostGIS 2.0 experimental builds 3) Use hard upgrade process. http://www.postgis.org/documentation/manual-svn/postgis_installation.html#ha rd_upgrade (Note: The windows upgrade link for windows specific instructions) ( http://trac.osgeo.org/postgis/wiki/UsersWikiWinUpgrade ) If we are talking January 2012 -- then 1 ) Install new binaries 2) Restore your backup -- some things might fail to restore, that's okay 3) Rung the postgis_upgrade_20_minor and rtpostgis_upgrade_20_minor.sql in the share/contrib folder of the experimental zip folder. Note: Some changes that require a dump restore have happened since we distributed the last experimental -- but those changes don't effect raster functionality and I plan to release a new build soon once I get my make check working again. Hope that helps, Regina _______________________________________________ postgis-users mailing list [email protected] http://postgis.refractions.net/mailman/listinfo/postgis-users
_______________________________________________ postgis-users mailing list [email protected] http://postgis.refractions.net/mailman/listinfo/postgis-users
