pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Michiel Lange <michiel@minas.demon.nl>
To: pgsql-admin@postgresql.org
Subject: Re: Upgrading
Date: Tue, 09 Mar 2004 08:18:37 +0100
Message-ID: <404D6FCD.6060501@minas.demon.nl> (raw)
In-Reply-To: <Pine.LNX.4.33.0403081243160.2365-100000@css120.ihs.com>
References: <Pine.LNX.4.33.0403081243160.2365-100000@css120.ihs.com>

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 <all your needed flags>
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 
<bladidbla>
(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
>
>  
>




view thread (4+ messages)

Message-ID: <404D6FCD.6060501@minas.demon.nl>
Permalink:  ../404D6FCD.6060501@minas.demon.nl/
Also on:    postgresql.org/message-id/404D6FCD.6060501@minas.demon.nl

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: michiel@minas.demon.nl
  Subject: Re: Upgrading
  In-Reply-To: <404D6FCD.6060501@minas.demon.nl>
  References: <Pine.LNX.4.33.0403081243160.2365-100000@css120.ihs.com> <404D6FCD.6060501@minas.demon.nl>

* 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