Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 78C1B2E0032 for ; Tue, 12 Feb 2008 03:56:22 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 76018-07 for ; Tue, 12 Feb 2008 03:56:19 -0400 (AST) Received: from hu-out-0506.google.com (hu-out-0506.google.com [72.14.214.225]) by postgresql.org (Postfix) with ESMTP id 03BD22E002F for ; Tue, 12 Feb 2008 03:56:17 -0400 (AST) Received: by hu-out-0506.google.com with SMTP id 22so7644268hug.23 for ; Mon, 11 Feb 2008 23:56:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:subject:cc:in-reply-to:mime-version:content-type:references; bh=HwuECUnU2wgpuRCeF6402y4cyl9ZEwndoCJ3wM7Dv2w=; b=gQokqe84XO4bct5EIJJ5WClfeN/KjossmnJ6iWVf1pklih1oz8jM+Mx57AzCpQUvXTCnEmTnroFPNzZ0dw+FJspper3YUu703kagqkKrNjzqcwmVdYVymUJne+/ErbSkng2KPEpO2A9repcZOspblRg7kxxLEqBkrzffbjuAZ14= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:subject:cc:in-reply-to:mime-version:content-type:references; b=C2WbsVnWnr9tA3e5LlnmaqblNeNhVMoSYa+xuLCDSCzpui4arqsjanB8jSELjLVkwLcHm+B72huIaYr+4FGH3m13Ta+1XKK/GxRs6t6j6m48S5UKHCfhO2Kh4VSf0UjwQcnSsHzIjBh3VT2I+qb49l/0p4OsOlIpsvcrcQq8M2s= Received: by 10.78.201.2 with SMTP id y2mr1735489huf.56.1202802976370; Mon, 11 Feb 2008 23:56:16 -0800 (PST) Received: by 10.78.150.15 with HTTP; Mon, 11 Feb 2008 23:56:16 -0800 (PST) Message-ID: Date: Tue, 12 Feb 2008 07:56:16 +0000 From: "Peter Childs" Subject: Re: 8.3.0 upgrade, confused by documentation Cc: pgsql-admin@postgresql.org In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_46874_32847601.1202802976363" References: <47B0A63A.9040807@otg-nc.com> <9999.1202765994@sss.pgh.pa.us> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/147 X-Sequence-Number: 28221 ------=_Part_46874_32847601.1202802976363 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On 11/02/2008, Tena Sakai 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@gallo.ucsf.edu > > > -----Original Message----- > From: Tom Lane [mailto:tgl@sss.pgh.pa.us ] > Sent: Mon 2/11/2008 1:39 PM > To: Chander Ganesan > Cc: Tena Sakai; pgsql-admin@postgresql.org > Subject: Re: [ADMIN] 8.3.0 upgrade, confused by documentation > > Chander Ganesan 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 > > ------=_Part_46874_32847601.1202802976363 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline

On 11/02/2008, Tena Sakai <tsakai@gallo.ucsf.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@gallo.ucsf.edu


-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Mon 2/11/2008 1:39 PM
To: Chander Ganesan
Cc: Tena Sakai; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] 8.3.0 upgrade, confused by documentation

Chander Ganesan <chander@otg-nc.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


------=_Part_46874_32847601.1202802976363--