Changes between Version 3 and Version 4 of NetDRMSInPostgres9

Timestamp:

08/06/14 12:21:10 (10 years ago)

Author:

jennifer

Comment:

--

NetDRMSInPostgres9

@@ -4 +4 @@
 That said, the most compelling reason for not updating Postgres is if you are running Slony replication as an active master.  If you are a "Slony master", such as the JSOC at Stanford, then you cannot support Slony 1.x against Postgres 9.2.  Stanford's replication processes at this time require Slony 1.2, and Postgres 8.4.x is the last version supported for that particular Slony version.  However, if you are only a passive Slony recipient, getting slony files and database changes but never issuing any yourself, then you are not confined to any particular database version.  Before making any change you should first have a conversation with your systems administrator and your department about changing their database since they might have rules or scripts that require testing.  
 
-If you're reading this and have decided to go forward with your 9.x compile, read further.  The author of this wiki page has only compiled as far as 9.2.  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, the following may be of use.  
+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 9.2.  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, the following may be of use.  
 
 Compiling NetDRMS v.7 against Postgres 9.2 requires changing one line in the SUMS code, and ensuring config.local has the right paths (file located in the top netdrms source directory).  It may also require changes to local environment variables if you have an existing Postgres 8.4.x installed on the machine.