Changes between Version 6 and Version 7 of NetDRMSInPostgres9

Timestamp:

08/06/14 12:30:15 (10 years ago)

Author:

jennifer

Comment:

--

NetDRMSInPostgres9

@@ -1 @@
-Should I compile NetDRMS against Postgres 9.x?
+= Should I compile NetDRMS against Postgres 9.x? =
 
 If you can, you probably should.  As of late July 2014, Postgres will not support version 8.4 past 8.4.22.  There will be no more patches.  For those on federal facilities, "no more patches" means you will be mandated to upgrade the program or you will have lots of explaining to do.  
@@ -6 +6 @@
 If you're reading this and have decided to go forward with your 9.x compile, changes required are minimal.  The author of this wiki page has only compiled as far as Postgres 9.2 and NetDRMS 7.  It is possible that further changes could be necessary for versions > 9.2 and your situation may be different.  However, for a NetDRMS 7 compilation against Postgres 9.2, you will need to:  
 
-*Change one line in two places in the SUMS code
+== Change one line in two places in the SUMS code ==
 
 Change two files in base/sums/libs/pg    named SUMLIB_RmDo.pgc and SUMLIB_RmDoX.pgc  and make this modification to line 9
@@ -15 +15 @@
 
 
-*Ensure config.local has the right paths listed for Postgres-specific variables (config.local file is located in the top netdrms source directory).  
+== Change config.local ==
+Ensure config.local has the right paths listed for Postgres-specific variables (config.local file is located in the top netdrms source directory).  
 
-*Possibly make changes to local environment variables if you have an existing Postgres 8.4.x installed on the machine.  
+== Local environment variables ==
+You may need to make changes to local environment variables if you have an existing Postgres 8.4.x installed on the machine.  
 
 If you already have a prior version of Postgres installed and want to compile NetDRMS against v. 9.x instead, set your $PATH and $LD_LIBRARY_PATH variables properly to reflect the Postgres 9.2 paths.  You might want to do this a .profile file and source it every time you log in to avoid confusing errata later.  
+
+== Backup ==
+If you are doing this on the primary data server, first slap your own hand and then go work on a test bed machine.  If that is unavailable, then do a full backup of your production database, and be certain you've configured Postgres 9 to run on two different ports (one for the drms database and another for the sums database).  Make doubly sure that all your usual keyboard shortcuts and aliases are re-worked (perhaps in a new .profile or .login file) to reference the new database compiling environment.  Better safe than sorry.  
 
 There you go - that's all that is required.