|
From: | Busser, Jim |
Subject: | Re: [Gnumed-devel] upgrade to 1.4 |
Date: | Wed, 13 Nov 2013 18:19:40 +0000 |
Hi Vaibhav,
Depending on the replies of other people (after this one), I can later try adding more information.
The following answers may need adjusting for Windows.
If you are already running Postgres 9.1 or higher (9.2x apparently being suggested), then it is as simple as follows:
- you should make backup dumps of your data
- you should quit all GNUmed and psql terminal sessions
- you will need the password for
postgres (postgres?)
gm-dbo (gm-dbo?)
root (or maybe sudo, or sudo -i, will suffice)
If anything about the attempted upgrade to v19 did not go as planned, you can STILL use your GNUmed 1.3x client and your v18 database, which will not have been changed by the upgrade.
So long as you are careful, you could enforce on yourself a discipline that anything you put in through client 1.4 is only for testing (perhaps do all your testing of the new version on Spock and Kirk) while continuing to use the client versions 1.3.x
which as long as you did not edit them will continue to put your new production data into v18.
Then, when you are ready, you can make a new backup of your production v18 database, and redo the server upgrade
18 19
and this will bring your 1.3.x client (v18 database) information up into v19 and will destroy any changes you made to Kirk and Spock and friends, which you did not care to keep, anyway.
Does the above help?
If you are using a version of Postgres below 9.1, a few more answers are necessary. For me, from the command line,
psql --version
returns --> psql (PostgreSQL) 8.4.9
psql -U postgres -c 'SELECT version();'
returns --> PostgreSQL 8.4.8 on i386-apple-darwin, compiled by GCC i686-apple-darwin8-gcc-4.0.1 (GCC) 4.0.1 (Apple Computer, Inc. build 5370), 32-bit
(1 row)
-- Jim
On 2013-11-13, at 9:14 AM, Vaibhav Banait <address@hidden> wrote:
|
[Prev in Thread] | Current Thread | [Next in Thread] |