From: Phillip Smith <phillip.smith@weatherbeeta.com.au>
To: 'Chris Hoover' <revoohc@gmail.com>
To: pgsql-admin@postgresql.org
Subject: Re: Upgrading from 7.2.1 to 8.x
Date: Thu, 1 Nov 2007 08:48:15 +1100
Message-ID: <007e01c81c07$bdb45500$9b0014ac@wbaus090> (raw)
In-Reply-To: <1d219a6f0710311028s745446aay7dd59c1982af7b03@mail.gmail.com>
You can have a look through all the release notes from 7.2.1 to current to
see what will be fixed, including any data eating insects. Check this page
http://www.postgresql.org/docs/7.4/static/release.html
Obviously you'll need to test everything, but you should be able to install
the new version, use pg_dumpall to dump your DB, and then restore it to the
new version. Any errors that come up will need to be investigated.
-----Original Message-----
From: pgsql-admin-owner@postgresql.org
[mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Chris Hoover
Sent: Thursday, 1 November 2007 04:28
To: pgsql-admin@postgresql.org Admin
Subject: [ADMIN] Upgrading from 7.2.1 to 8.x
Question,
I have an ancient database that is running Postgresql 7.2.1 on AIX. Is it
safe to directly upgrade the database to 8.1? If not, what steps do I need
to take?
I have been pushing for 3 years to upgrade this database, and with some
upcoming projects, I am going to do another push with management to upgrade
this database.
Also, I know there are a ton of fixes/improvements from 7.2, but are there
any major data losing bugs in this version that I can use as added pressure
on management?
Thanks,
Chris
THINK BEFORE YOU PRINT - Save paper if you don't really need to print this
*******************Confidentiality and Privilege Notice*******************
The material contained in this message is privileged and confidential to
the addressee. If you are not the addressee indicated in this message or
responsible for delivery of the message to such person, you may not copy
or deliver this message to anyone, and you should destroy it and kindly
notify the sender by reply email.
Information in this message that does not relate to the official business
of Weatherbeeta must be treated as neither given nor endorsed by Weatherbeeta.
Weatherbeeta, its employees, contractors or associates shall not be liable
for direct, indirect or consequential loss arising from transmission of this
message or any attachments
e-mail.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: phillip.smith@weatherbeeta.com.au, revoohc@gmail.com
Subject: Re: Upgrading from 7.2.1 to 8.x
In-Reply-To: <007e01c81c07$bdb45500$9b0014ac@wbaus090>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox