From: | Gabriele Bartolini <Gabriele(dot)Bartolini(at)2ndQuadrant(dot)it> |
---|---|
To: | Iñigo Martinez Lasala <imartinez(at)vectorsf(dot)com> |
Cc: | Silvio Brandani <silvio(dot)brandani(at)tech(dot)sdb(dot)it>, <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: upgrade postgres 8.1.21 to version 8.3.6 |
Date: | 2010-07-14 07:50:41 |
Message-ID: | c3e15c443c8ea72f2a036f047b2d3161@mail.xcon.it |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Ciao Silvio,
On Tue, 13 Jul 2010 22:52:51 +0200, Iñigo Martinez Lasala
> You should script database migration process in order to make it faster.
> Upgrading binaries is really simple. A yum upgrade should be enough.
Yes, faster and repeatable. Something you can launch with a script that
does everything from scratch. As Iñigo was pointing out, you must pay a lot
of attention in setting up a test environment which helps you:
* simulate the migration process (and gives you accurate measures of
times)
* test the applications
As Iñigo said, on a typical usage pattern, the most likely set of errors
you will encounter are data type checks which require casting. Therefore it
becomes crucial to:
* setup the test database (preferably on a different server)
* setup test applications that interface with the new Postgres database
I assume you are using 8.3 because of RPM availability, isn't it?
Otherwise, you should think of 8.4.
Ciao,
Gabriele
--
Gabriele Bartolini - 2ndQuadrant Italia
PostgreSQL Training, Services and Support
Gabriele(dot)Bartolini(at)2ndQuadrant(dot)it - www.2ndQuadrant.it
From | Date | Subject | |
---|---|---|---|
Next Message | Eduardo Sá dos Reis | 2010-07-14 13:48:16 | Error after upgrade 8.1.4 to 8.4.2 |
Previous Message | Iñigo Martinez Lasala | 2010-07-13 20:52:51 | Re: upgrade postgres 8.1.21 to version 8.3.6 |