Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 30F296500B4 for ; Mon, 8 Sep 2008 10:21:28 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 20328-07 for ; Mon, 8 Sep 2008 10:21:22 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from smadev.internal.net (host3.dynacom.ondsl.gr [62.103.35.211]) by postgresql.org (Postfix) with ESMTP id 2DADD650080 for ; Mon, 8 Sep 2008 10:21:21 -0300 (ADT) Received: from smadev.internal.net (localhost [127.0.0.1]) by smadev.internal.net (8.14.2/8.14.2) with ESMTP id m88DLEg9000716; Mon, 8 Sep 2008 16:21:14 +0300 (EEST) (envelope-from achill@matrix.gatewaynet.com) Received: from localhost (localhost [[UNIX: localhost]]) by smadev.internal.net (8.14.2/8.14.2/Submit) id m88DLAro000715; Mon, 8 Sep 2008 16:21:10 +0300 (EEST) (envelope-from achill@matrix.gatewaynet.com) From: Achilleas Mantzios Organization: Dynacom Tankers Mgmt To: pgsql-admin@postgresql.org Subject: Re: update to 8.3.3 Date: Mon, 8 Sep 2008 16:20:38 +0300 User-Agent: KMail/1.9.7 Cc: Devrim =?utf-8?q?G=C3=9CND=C3=9CZ?= , Jumping References: <1220879669.2711.28.camel@laptop.gunduz.org> In-Reply-To: <1220879669.2711.28.camel@laptop.gunduz.org> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200809081621.10713.achill@matrix.gatewaynet.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200809/64 X-Sequence-Number: 30157 =CE=A3=CF=84=CE=B9=CF=82 Monday 08 September 2008 16:14:29 =CE=BF/=CE=B7 De= vrim G=C3=9CND=C3=9CZ =CE=AD=CE=B3=CF=81=CE=B1=CF=88=CE=B5: > On Mon, 2008-09-08 at 11:35 +0800, Jumping wrote: > > I plan to update my database from 8.1.9 to 8.3.3. > > Is there any tricks or tips ? >=20 > I would first update to 8.1.13, then go on. Hehe i upgraded from 7.4 to 8.3.3 and it was a big pain, but since i survived i'd say 8.1.9->8.3.3 is at least safe! It all depends on the quality (standard-wise) of the original SQL code howe= ver. >=20 > Anysay, Read the release notes, and check for any possible > incompatibility issues.=20 >=20 > http://www.postgresql.org/docs/current/static/release-8-3.html > http://www.postgresql.org/docs/current/static/release-8-2.html >=20 > I believe you should first check the casting changes in 8.3 . >=20 > Regards, =2D-=20 Achilleas Mantzios