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 48636D1B9E5 for ; Tue, 9 Mar 2004 07:22:38 +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 42927-02 for ; Tue, 9 Mar 2004 03:22:36 -0400 (AST) Received: from smurfer.pastoraat (minas-2.demon.nl [212.238.194.105]) by svr1.postgresql.org (Postfix) with ESMTP id E0732D1B9AF for ; Tue, 9 Mar 2004 03:22:33 -0400 (AST) Received: from minas.demon.nl (athlon.pastoraat [192.168.1.1]) by smurfer.pastoraat (8.12.8/8.12.8) with ESMTP id i297QBhv012967 for ; Tue, 9 Mar 2004 08:26:11 +0100 Message-ID: <404D6FCD.6060501@minas.demon.nl> Date: Tue, 09 Mar 2004 08:18:37 +0100 From: Michiel Lange User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: Upgrading References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/141 X-Sequence-Number: 12710 I have ever used Slackware, so no rpm's for me... gives me some control on what to include and what not... but it learned me how to do compile stuff ;-) Here is what I would do: locate all Postgresql binaries. I suppose it's in /usr/bin dump _all_ your data (maybe stopping the postmaster and making a filesystem backup is the most certain way to do this) download postgres sources and 7.2.5 rpm shutdown the postmaster upgrade to 7.2.5 by rpm start postmaster dump _all_ your data if succesfull look for any other configuration files and store them separately (there may be something in /etc and /etc/rc.d ...) unpack 7.4 sources ./configure --help to see all the flags you can set ./configure if succesfull: make if succesfull: stop postmaster uninstall postgres 7.2.5 with rpm make install the sources initdb start postmaster restore your data check all config files and see if they're still the same, check /etc/rc.d startup stuff too (I honestly must say I have no idea how this is really implemented) enjoy! Mind: you can also do the following starting from the ./configure part, all that was to be done previously still applies: stop postmaster uninstall postgres 7.2.5 with rpm ./configure --with-all-your-flags && make && make install && initdb -D (make will only run if configure was succesfull, make install will only run when make was succesfull and so on) If this is a first-timer, try this out on a non-critical system where everything may fail! If it's not a first-timer you might still want to do that, since one easily forgets a flag or two or makes a slight mistake. Storing all your commands in a shell-script makes it easier to do exactly the same stuff on another machine... Hope it helps... Michiel scott.marlowe wrote: >On Thu, 4 Mar 2004, Indibil wrote: > > > >>Hi: >> >>I have a PostgreSQL 7.2.2 running in a Linux Mandrake 8.2 Server. >>I want to upgrade to PostgreSQL 7.3 >>I would like to accomplish this by installing fit rpm packages, because my >>linux skills are limited. >>However, there aren't any packages of PostgreSQL 7.3 for Mandrake 8.2 >>I must be careful because the database is in a production environment. >>What would be the best way to upgrade? >> >> > >Unless there is a known problem for you with 7.4, I'd recommend upgrading >to that. 7.4.2 is due out soon (today or something like it) and it is >a much easier upgrade than 7.2 to 7.3 was. > >You might want to upgrade to 7.2.5 first though, as there were some issues >with early 7.2s upgrading to 7.4 I remember running into. > >I don';t use RPMs for postgresql, so I'm not much help there. > > >---------------------------(end of broadcast)--------------------------- >TIP 6: Have you searched our list archives? > > http://archives.postgresql.org > > >