9 | | 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. If you are upgrading from an 8.4.x database, recall that you are undergoing a major version change and that involves "data migration". You may find that the migration tool provided by Postgres is unsuccessful. If so, you may need to migrate your data using a plain-text format data dump (with SQL "insert" commands). Check the Postgres website for migration options and do some testing before assuming the 9.2.x database is fully ready. Better safe than sorry. |
| 9 | 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. If you are upgrading from an 8.4.x database, recall that you are undergoing a major version change and that involves "data migration". You may find that the migration tool provided by Postgres, pg_upgrade, is unsuccessful. If so, you may need to migrate your data using a plain-text format data dump (with SQL "insert" commands). Check the Postgres website for migration options ([http://www.postgresql.org/docs/9.2/static/upgrading.html]) and do some testing before assuming the 9.2.x database is fully ready. Better safe than sorry. |