From raul@zerosoft.ro Tue Mar 23 10:45:29 2004 X-Original-To: pgsql-php-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 22016D1DC5D for ; Tue, 23 Mar 2004 10:45:29 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 87576-06 for ; Tue, 23 Mar 2004 06:45:29 -0400 (AST) Received: from mail.zerosoft.ro (main.zerosoft.ro [193.226.89.14]) by svr1.postgresql.org (Postfix) with ESMTP id C98F5D1DBAF for ; Tue, 23 Mar 2004 06:45:18 -0400 (AST) Received: from 192.168.16.10 by mail.zerosoft.ro ([192.168.16.1] running VPOP3) with SMTP for ; Tue, 23 Mar 2004 12:55:38 +0200 Message-ID: <001301c410c5$60c10240$0a10a8c0@zerosoft.ro> Reply-To: "Raul Secan" From: "Raul Secan" To: Subject: upgrading to 7.4.2 Date: Tue, 23 Mar 2004 12:55:39 +0200 Organization: ZEROSOFT MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0010_01C410D6.24423120" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Server: VPOP3 V1.4.5 - Registered to: ZeroSoft X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.1 tagged_above=0.0 required=5.0 tests=HTML_MESSAGE X-Spam-Level: X-Archive-Number: 200403/55 X-Sequence-Number: 2654 This is a multi-part message in MIME format. ------=_NextPart_000_0010_01C410D6.24423120 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, can anyone tell me the exact steps to upgrading from 7.4.1 to 7.4.2. I didn't upgrade PostgreSQL until now, but I need to do that now, so I don'= t want to brake something. Thanks, Raul Secan. ------=_NextPart_000_0010_01C410D6.24423120 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello, can anyone tell me the exact steps = to=20 upgrading from 7.4.1 to 7.4.2.
I didn't upgrade PostgreSQL until now, but= I need=20 to do that now, so I don't want to brake something.
 
Thanks, Raul Secan.
------=_NextPart_000_0010_01C410D6.24423120-- From bruno@wolff.to Tue Mar 23 15:47:40 2004 X-Original-To: pgsql-php-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 8609FD1C4EB for ; Tue, 23 Mar 2004 15:47:40 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 18462-09 for ; Tue, 23 Mar 2004 11:47:42 -0400 (AST) Received: from wolff.to (wolff.to [66.93.249.74]) by svr1.postgresql.org (Postfix) with SMTP id 00A65D1B97B for ; Tue, 23 Mar 2004 11:47:37 -0400 (AST) Received: (qmail 23201 invoked by uid 500); 23 Mar 2004 15:50:41 -0000 Date: Tue, 23 Mar 2004 09:50:41 -0600 From: Bruno Wolff III To: Raul Secan Cc: pgsql-php@postgresql.org Subject: Re: upgrading to 7.4.2 Message-ID: <20040323155041.GA22109@wolff.to> Mail-Followup-To: Raul Secan , pgsql-php@postgresql.org References: <001301c410c5$60c10240$0a10a8c0@zerosoft.ro> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <001301c410c5$60c10240$0a10a8c0@zerosoft.ro> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/56 X-Sequence-Number: 2655 On Tue, Mar 23, 2004 at 12:55:39 +0200, Raul Secan wrote: > Hello, can anyone tell me the exact steps to upgrading from 7.4.1 to 7.4.2. > I didn't upgrade PostgreSQL until now, but I need to do that now, so I don't want to brake something. Pretty much you just need to shutdown the database before installing the new binaries. You don't have to do a dump and restore. However, you want to read the 7.4.2 release notes as a dump, initdb and restore may be the easiest way for you to fix one of the problems fixed in 7.4.2. From bruno@wolff.to Wed Mar 24 17:23:11 2004 X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 09C16D1ECB9 for ; Wed, 24 Mar 2004 17:23:11 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 15046-07 for ; Wed, 24 Mar 2004 13:23:07 -0400 (AST) Received: from wolff.to (wolff.to [66.93.249.74]) by svr1.postgresql.org (Postfix) with SMTP id 77359D1ECD3 for ; Wed, 24 Mar 2004 13:23:06 -0400 (AST) Received: (qmail 11807 invoked by uid 500); 24 Mar 2004 17:26:08 -0000 Date: Wed, 24 Mar 2004 11:26:08 -0600 From: Bruno Wolff III To: Raul Secan Cc: pgsql-admin@postgresql.org Subject: Re: [PHP] upgrading to 7.4.2 Message-ID: <20040324172608.GB11352@wolff.to> Mail-Followup-To: Raul Secan , pgsql-admin@postgresql.org References: <001301c410c5$60c10240$0a10a8c0@zerosoft.ro> <20040323155041.GA22109@wolff.to> <000701c410f2$775efb60$0a10a8c0@zerosoft.ro> <20040323162112.GA24078@wolff.to> <005301c41177$61c3d160$0a10a8c0@zerosoft.ro> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <005301c41177$61c3d160$0a10a8c0@zerosoft.ro> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/312 X-Sequence-Number: 12881 I am copying this back to the admin list to keep the discussion where more people can comment. (The admin list is more appropiate than the PHP list where your initial questions were posted.) On Wed, Mar 24, 2004 at 10:09:51 +0200, Raul Secan wrote: > What I mean is that this is the only posibility to upgrade Postgres, by > deleting the old one and installing the new one? > > Isn't there an easy way to upgrade this database server (for example MySQL's > upgrade is very easy to do: rpm -Uvh mysql.xxxxx.rpm)? If you have rpms for 7.4.2 you can do the update that way. That just replaces the binaries, it doesn't do anything to the data. That technique will work as long as you are doing an upgrade between two minor releases of the same major release. You have to do a dump first if you are changing major release version. Also you should read the release notes for 7.4.2 as there are some special instructions in this case. From DGoulet@vicr.com Wed Mar 24 17:45:15 2004 X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 18A03D1ECD8 for ; Wed, 24 Mar 2004 17:45:15 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 26462-05 for ; Wed, 24 Mar 2004 13:45:13 -0400 (AST) Received: from smtpgate.vicr.com (smtpgate.vicr.com [207.141.187.5]) by svr1.postgresql.org (Postfix) with ESMTP id 7D28BD1DB94 for ; Wed, 24 Mar 2004 13:45:11 -0400 (AST) Received: from 25exch1.vicorpower.vicr.com ([172.20.20.30]) by exchgate.vicorpower.vicr.com with Microsoft SMTPSVC(5.0.2195.5329); Wed, 24 Mar 2004 12:44:06 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP] upgrading to 7.4.2 Date: Wed, 24 Mar 2004 12:44:06 -0500 Message-ID: <4001DEAF7DF9BD498B58B45051FBEA656D82F6@25exch1.vicorpower.vicr.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [ADMIN] [PHP] upgrading to 7.4.2 Thread-Index: AcQRxoyxZ9q211gJQCm3h9TvvtYTFwAAI0FA From: "Goulet, Dick" To: "Bruno Wolff III" , "Raul Secan" Cc: X-OriginalArrivalTime: 24 Mar 2004 17:44:06.0473 (UTC) FILETIME=[9AB1E390:01C411C7] X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/313 X-Sequence-Number: 12882 Comparing a MySql upgrade to anything else is comparing apples to eggplants= . Their not even in the same group. mySql likes to leave their datafiles = alone making all of their changes in the binaries. Now while that is good = from an upgrade standpoint, what do you upgrade for? New Features. MySql = doesn't like new features as it will "slow down the database". Dick Goulet Senior Oracle DBA Oracle Certified 8i DBA -----Original Message----- From: Bruno Wolff III [mailto:bruno@wolff.to] Sent: Wednesday, March 24, 2004 12:26 PM To: Raul Secan Cc: pgsql-admin@postgresql.org Subject: Re: [ADMIN] [PHP] upgrading to 7.4.2 I am copying this back to the admin list to keep the discussion where more people can comment. (The admin list is more appropiate than the PHP list where your initial questions were posted.) On Wed, Mar 24, 2004 at 10:09:51 +0200, Raul Secan wrote: > What I mean is that this is the only posibility to upgrade Postgres, by > deleting the old one and installing the new one? >=20 > Isn't there an easy way to upgrade this database server (for example MySQ= L's > upgrade is very easy to do: rpm -Uvh mysql.xxxxx.rpm)? If you have rpms for 7.4.2 you can do the update that way. That just replac= es the binaries, it doesn't do anything to the data. That technique will work as long as you are doing an upgrade between two minor releases of the same major release. You have to do a dump first if you are changing major release version. Also you should read the release notes for 7.4.2 as there are some special instructions in this case. ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org From cbbrowne@acm.org Wed Mar 24 21:55:25 2004 X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 75DE6D1EBFE for ; Wed, 24 Mar 2004 21:55:25 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 20023-08 for ; Wed, 24 Mar 2004 17:55:24 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 7CE5FD1EAF8 for ; Wed, 24 Mar 2004 17:55:22 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.12.9/8.12.9) with ESMTP id i2OLtL1Y006070 for ; Wed, 24 Mar 2004 21:55:21 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id i2OLoefs005301 for pgsql-admin@postgresql.org; Wed, 24 Mar 2004 21:50:40 GMT From: Christopher Browne X-Newsgroups: comp.databases.postgresql.admin Subject: Re: [PHP] upgrading to 7.4.2 Date: Wed, 24 Mar 2004 16:09:05 -0500 Organization: cbbrowne Computing Inc Lines: 20 Message-ID: References: <4001DEAF7DF9BD498B58B45051FBEA656D82F6@25exch1.vicorpower.vicr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@news.hub.org X-message-flag: Outlook is rather hackable, isn't it? X-Home-Page: http://www.cbbrowne.com/info/ X-Affero: http://svcs.affero.net/rm.php?r=cbbrowne User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Security Through Obscurity, linux) Cancel-Lock: sha1:WNhNK6BSx/EqlWpt49PJXj99xL4= To: pgsql-admin@postgresql.org X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/334 X-Sequence-Number: 12903 Quoth DGoulet@vicr.com ("Goulet, Dick"): > Comparing a MySql upgrade to anything else is comparing apples to > eggplants. Their not even in the same group. mySql likes to leave > their datafiles alone making all of their changes in the binaries. > Now while that is good from an upgrade standpoint, what do you > upgrade for? New Features. MySql doesn't like new features as it > will "slow down the database". Oh, but that's not true anymore. MySQL(tm) is supposed to support subqueries, stored procedures, triggers, and views Real Soon Now... And remember, their reason for being is to provide "the world's most popular open source database." If popularity requires dressing up in slower clothing, well, that's presumably going to happen... -- let name="cbbrowne" and tld="acm.org" in String.concat "@" [name;tld];; http://cbbrowne.com/info/nonrdbms.html Rules of the Evil Overlord #228. "If the hero claims he wishes to confess in public or to me personally, I will remind him that a notarized deposition will serve just as well."