Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 632129FBF0C for ; Wed, 31 Oct 2007 19:44:50 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 30533-02-6 for ; Wed, 31 Oct 2007 19:44:03 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from weatherbeeta.com.au (218-214-212-153.people.net.au [218.214.212.153]) by postgresql.org (Postfix) with ESMTP id 024829FC711 for ; Wed, 31 Oct 2007 18:48:15 -0300 (ADT) Received: (qmail 25699 invoked from network); 31 Oct 2007 21:48:12 -0000 X-NetworkBox-HamSign: 0101;OUT;wbeetaau1;3c897f3df7052723ae01ca9836ea84c8; Received: from unknown (HELO mail.weatherbeeta.com.au) (10.20.0.2) by 10.20.0.254 with SMTP; 31 Oct 2007 21:48:12 -0000 Received: (qmail 30298 invoked by uid 1166); 1 Nov 2007 08:48:06 +1100 Received: from 172.20.0.155 by mail.weatherbeeta.com.au (envelope-from , uid 1165) with qmail-scanner-1.25-st-qms (clamdscan: 0.88.6/2315. perlscan: 1.25-st-qms. Clear:RC:1(172.20.0.155):. Processed in 0.417166 secs); 31 Oct 2007 21:48:06 -0000 X-Antivirus-mail.weatherbeeta.com.au-Mail-From: phillip.smith@weatherbeeta.com.au via mail.weatherbeeta.com.au X-Antivirus-mail.weatherbeeta.com.au: 1.25-st-qms (Clear:RC:1(172.20.0.155):. Processed in 0.417166 secs Process 30285) Received: from it-phil.weatherbeeta.com.au (HELO wbaus090) (172.20.0.155) by mail.weatherbeeta.com.au with SMTP; 1 Nov 2007 08:48:04 +1100 From: "Phillip Smith" To: "'Chris Hoover'" , Subject: Re: Upgrading from 7.2.1 to 8.x Date: Thu, 1 Nov 2007 08:48:15 +1100 Organization: Weatherbeeta Pty Ptd Message-ID: <007e01c81c07$bdb45500$9b0014ac@wbaus090> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_007F_01C81C63.F124CD00" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 In-Reply-To: <1d219a6f0710311028s745446aay7dd59c1982af7b03@mail.gmail.com> Importance: Normal X-Scanned-By-wbeetaau1: Virus scan performed by network-box X-Scanned-By-wbeetaau1: Scanner file id is wbeetaau1-1193867292.864-25692-000 X-Scanned-By-wbeetaau1: No known viruses found in message (received+scanned in 0.03/0.05 secs) X-Scanned-By-wbeetaau1: Spam-Check-Result: No, hits=0 required=7 tests= autolearn=no version=2.0 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.097 tagged_above=0 required=5 tests=AWL=-0.290, BAYES_05=-1.11, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396, RDNS_DYNAMIC=0.1 X-Spam-Level: X-Archive-Number: 200710/327 X-Sequence-Number: 27241 This is a multi-part message in MIME format. ------=_NextPart_000_007F_01C81C63.F124CD00 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit 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. ------=_NextPart_000_007F_01C81C63.F124CD00 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

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://ww= w.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


=

=0ATHINK BEFORE YOU PRINT - Save paper if you don't really need to print t= his e-mail.=0A

=0A*******************Confidentiality and Privilege Notice**= *****************=0A

=0AThe material contained in this message is privileg= ed and confidential to=0Athe addressee. If you are not the addressee indicate= d in this message or=0Aresponsible for delivery of the message to such person,= you may not copy=0Aor deliver this message to anyone, and you should destroy = it and kindly=0Anotify the sender by reply email.=0A

=0AInformation in this mess= age that does not relate to the official business=0Aof Weatherbeeta must be tr= eated as neither given nor endorsed by Weatherbeeta.=0AWeatherbeeta, its emplo= yees, contractors or associates shall not be liable=0Afor direct, indirect or = consequential loss arising from transmission of this=0Amessage or any attachme= nts=0A
= ------=_NextPart_000_007F_01C81C63.F124CD00--