Re: 8.3.0 upgrade, confused by documentation

From: "Peter Childs" <peterachilds(at)gmail(dot)com>
To:
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: 8.3.0 upgrade, confused by documentation
Date: 2008-02-12 07:56:16
Message-ID: a2de01dd0802112356k44c0161dr3ad7609d3a59e629@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On 11/02/2008, Tena Sakai <tsakai(at)gallo(dot)ucsf(dot)edu> wrote:
>
> Hello Tom,
>
> > If your platform doesn't make it easy to
> > have two versions installed concurrently,
> > one simple way to do this is to install
> > the newer PG code on another machine and
> > do the dump across the network.
>
> I am using Dell Hardware on Redhat Enterprise
> Linux and wanting to go from 8.2.4 to 8.3.0.
> Would you please tell me where I might find
> documentation/references to run multiple versions
> of postgreSQL on one OS?
>

Put simply carry out step 4 first then return to step 1 and carry out the
rest in order skipping step 4 as you have already done that.

If you wish you could init the db somewhere else (different path after -d)
change the config to run on a different port then pipe pg_dump to psql
something like however this is a bit risky unless you understand
postgresql,conf properly....

/usr/local/pgsql/bin/psql -p 5433 -d postgres -f
`/usr/local/pgsql/bin/pg_dumpall`

or

Put simply carry out step 4 first then return to step 1 and carry out the
rest in order skipping step 4 as you have already done that. It is also
worth running ./configure --prefix /usr/local/pgsql-8.3.0 and then make
/usr/local/pgsql a symlink (ln -s pgsql-8.3.0 /usr/local/pgsql) then all you
need to do to switch versions is stop postgres switch the symlink and
restart, (Very handy when doing a minor version upgrade and wanting to keep
downtime to a minumum! but will not work across major versin upgrades)

If you wish you could init the db somewhere else (different path after -d)
change the config to run on a different port then pipe pg_dump to psql
however this is a bit risky unless you understand postgresql,conf properly
The pipe can also cause problems as the reload may take much longer than the
dump and the two together will be slower.

Peter Childs

Regards,
>
> Tena Sakai
> tsakai(at)gallo(dot)ucsf(dot)edu
>
>
> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us <tgl(at)sss(dot)pgh(dot)pa(dot)us>]
> Sent: Mon 2/11/2008 1:39 PM
> To: Chander Ganesan
> Cc: Tena Sakai; pgsql-admin(at)postgresql(dot)org
> Subject: Re: [ADMIN] 8.3.0 upgrade, confused by documentation
>
> Chander Ganesan <chander(at)otg-nc(dot)com> writes:
> > Tena Sakai wrote:
> >> I am going from 8.2.4 to 8.3.0. Does, "For best results,
> >> however, try to use the pg_dumpall command from PostgreSQL
> >> 8.3.0" apply to me?
> >>
> > Yes. You want to use the 8.3.0 version of pg_dumpall.
>
> I don't think this is particularly critical for 8.2 to 8.3, but in cases
> where you're trying to jump multiple major versions in one step, it's
> often the case that it will go smoother with the later pg_dump.
>
> If your platform doesn't make it easy to have two versions installed
> concurrently, one simple way to do this is to install the newer PG code
> on another machine and do the dump across the network.
>
> regards, tom lane
>
>

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Peter Eisentraut 2008-02-12 12:08:01 Re: postgres rpms for solaris and suse
Previous Message Michael Fuhr 2008-02-12 02:42:19 Re: [PERFORM] Question about CLUSTER