Changes between Version 2 and Version 3 of Ticket #84, comment 3


Ignore:
Timestamp:
May 24, 2018 4:44:19 PM (7 years ago)
Author:
cedric
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #84, comment 3

    v2 v3  
    7878TODO here 
    7979 
    80 Edit the script accordingly to your path settings. Note that utils folder is packaged with the PostGIS tar balls 
    81 if not present in your PostGIS install. Download the tar ball for the PostGIS you want to upgrade to and copy the utils folder to the same folder as your backup. ​http://postgis.net/source 
     80>> Edit the script accordingly to your path settings. Note that utils folder is packaged with the PostGIS tar balls 
     81>>if not present in your PostGIS install. Download the tar ball for the PostGIS you want to upgrade to and copy the utils folder to the same folder as your backup. ​>>http://postgis.net/source 
    8282 
    83 Right mouse click on the .bat file (you may have to choose -- Run as Administrator) or run if run as administrator is not available. 
    84 If all is working -- you should see a screen something like: 
    85 ALTER TABLE 
    86 ALTER TABLE 
    87 SET 
    88 Clicking enter after the process is done will close the batch script. 
     83>>Right mouse click on the .bat file (you may have to choose -- Run as Administrator) or run >>if run as administrator is not available. 
     84>>If all is working -- you should see a screen something like: 
     85>>ALTER TABLE 
     86>>ALTER TABLE 
     87>>SET 
     88>>Clicking enter after the process is done will close the batch script. 
    8989 
    90 When all is done, check the errors.txt file to see if there are any serious errors. Serious errors are tables that did not come back, or some of your own functions that did not come back, your specialty constraints and indexes. PostGIS function failures should not show, but if they do, you can ignore them. 
     90>>When all is done, check the errors.txt file to see if there are any serious errors. Serious >>errors are tables that did not come back, or some of your own functions that did not come >>back, your specialty constraints and indexes. PostGIS function failures should not show, but >>if they do, you can ignore them. 
     91> OK works for that database 
    9192 
    92