Thread: Ideal way to upgrade to postgres 8.3 with less downtime

Στις Friday 07 November 2008 08:04:05 ο/η Swathi S έγραψε:
> Hi,
>
> I have a database of size approx 400G. It's a 24/7 database. Only few tables
> have regular reads and writes. The other tables just store information.
>
> I would like to upgrade to 8.3 and would like to know the best way to
> upgrade with less downtime.
>
> Thanks
> Swathi
>

And now you are running with which version?
The ideal way is to read the HISTORY file, do several upgrade excercises on a test system with the
same database (e.g. with a recent backup of the original), and then plan/organize your actions.
But i must say that the older version of postgresql you run, the fancier things your apps do, and the more lines of
codethey have, 
the harder it will be to upgrade.
Usually SPI and JDBC require large amounts of work as well.
Well i dont mean to be pessimistic, but our 7.4 -> 8.3 upgrade was pretty painful.

--
Achilleas Mantzios

On Thu, Nov 6, 2008 at 11:04 PM, Swathi S <ss.postgres@gmail.com> wrote:
> Hi,
>
> I have a database of size approx 400G. It's a 24/7 database. Only few tables
> have regular reads and writes. The other tables just store information.
>
> I would like to upgrade to 8.3 and would like to know the best way to
> upgrade with less downtime.

Assuming you're running 8.0 or higher now, slony should provide you
with a one stop upgrade path with the minimum amount of downtime.  We
use it for our database which is smaller (~20 Gigs) but quite hard
working, with access around the clock, and we switched out 8.1 to 8.3
with abut 1 minute of downtime.