Received: from maia.hub.org (unknown [200.46.208.211])
	by mail.postgresql.org (Postfix) with ESMTP id BABF1632538
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Wed, 14 Apr 2010 17:28:55 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia,
	port 10024) with ESMTP id 63385-02 for
	<pgsql-admin-postgresql.org@mail.postgresql.org>;
	Wed, 14 Apr 2010 20:28:40 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from hermes.vectorsf.com (firewall.vectorsf.com [62.82.80.62])
	by mail.postgresql.org (Postfix) with ESMTP id 54DDA632B11
	for <pgsql-admin@postgresql.org>; Wed, 14 Apr 2010 17:28:44 -0300 (ADT)
Received: from localhost (localhost.localdomain [127.0.0.1])
	by hermes.vectorsf.com (Postfix) with ESMTP id 2DDFF11C0042;
	Wed, 14 Apr 2010 22:27:51 +0200 (CEST)
X-Virus-Scanned: amavisd-new at hermes.vectorsf.com
Received: from hermes.vectorsf.com ([127.0.0.1])
	by localhost (hermes.vectorsf.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ExPeXObiy4LM; Wed, 14 Apr 2010 22:27:47 +0200 (CEST)
Received: from [192.168.1.21] (unknown [87.223.74.199])
	(Authenticated sender: imartinez)
	by hermes.vectorsf.com (Postfix) with ESMTP id 80FF211C003E;
	Wed, 14 Apr 2010 22:27:46 +0200 (CEST)
Subject: Re: Migrating from 8.3 to 8.4 on the same server
From: =?ISO-8859-1?Q?I=F1igo?= Martinez Lasala <imartinez@vectorsf.com>
To: Lewis Kapell <lkapell@setonhome.org>
Cc: pgsql-admin@postgresql.org
In-Reply-To: <4BC5FB73.9@setonhome.org>
References: <4BC5FB73.9@setonhome.org>
Content-Type: multipart/alternative; boundary="=-USLgDqw5mJxj4bnEfstK"
Date: Wed, 14 Apr 2010 22:28:28 +0200
Message-ID: <1271276908.2780.39.camel@deimos>
Mime-Version: 1.0
X-Mailer: Evolution 2.28.3 
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-0.01 tagged_above=-10 required=5
	tests=BAYES_20=-0.001, HTML_MESSAGE=0.001, T_RP_MATCHES_RCVD=-0.01
X-Spam-Level: 
X-Archive-Number: 201004/178
X-Sequence-Number: 34272


--=-USLgDqw5mJxj4bnEfstK
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit

How big is your database?

If not very big, a pg_dump/pg_restore will be your best option. 8.3 to
8.4 is not a traumatic upgrade. In fact, it's really easy and probably
you won't need to change your database schema.
And pg_restore in 8.4 is really FAST (compared with previous versions).

-----Original Message-----
From: Lewis Kapell <lkapell@setonhome.org>
To: pgsql-admin@postgresql.org
Subject: [ADMIN] Migrating from 8.3 to 8.4 on the same server
Date: Wed, 14 Apr 2010 13:29:23 -0400


In the documentation under the heading "Migration Between Releases" we 
read:

<<It is also possible to use replication methods, such as Slony, to 
create a slave server with the updated version of PostgreSQL. The slave 
can be on the same computer or a different computer. [...] Such a 
switch-over results in only several seconds of downtime for an upgrade. >>

In the section "Warm Standby Servers for High Availability" it says:

<< For testing purposes, it is possible to run both primary and standby 
servers on the same system. >>

Although this section does not use the term Point-In-Time Recovery, I 
understand this is what it refers to.  Could the WAL/PITR method then be 
used to upgrade from 8.3 to 8.4 on the same server and avoid having the 
significant downtime of dump/restore?

If so, I understand the two servers would have to run on different 
ports.  Are there any other issues/traps to be aware of?

-- 

Thank you,

Lewis Kapell
Computer Operations
Seton Home Study School





--=-USLgDqw5mJxj4bnEfstK
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.28.3">
</HEAD>
<BODY>
How big is your database?<BR>
<BR>
If not very big, a pg_dump/pg_restore will be your best option. 8.3 to 8.4 is not a traumatic upgrade. In fact, it's really easy and probably you won't need to change your database schema.<BR>
And pg_restore in 8.4 is really FAST (compared with previous versions).<BR>
<BR>
-----Original Message-----<BR>
<B>From</B>: Lewis Kapell &lt;<A HREF="mailto:Lewis%20Kapell%20%3clkapell@setonhome.org%3e">lkapell@setonhome.org</A>&gt;<BR>
<B>To</B>: <A HREF="mailto:pgsql-admin@postgresql.org">pgsql-admin@postgresql.org</A><BR>
<B>Subject</B>: [ADMIN] Migrating from 8.3 to 8.4 on the same server<BR>
<B>Date</B>: Wed, 14 Apr 2010 13:29:23 -0400<BR>
<BR>
<PRE>
In the documentation under the heading &quot;Migration Between Releases&quot; we 
read:

&lt;&lt;It is also possible to use replication methods, such as Slony, to 
create a slave server with the updated version of PostgreSQL. The slave 
can be on the same computer or a different computer. [...] Such a 
switch-over results in only several seconds of downtime for an upgrade. &gt;&gt;

In the section &quot;Warm Standby Servers for High Availability&quot; it says:

&lt;&lt; For testing purposes, it is possible to run both primary and standby 
servers on the same system. &gt;&gt;

Although this section does not use the term Point-In-Time Recovery, I 
understand this is what it refers to.  Could the WAL/PITR method then be 
used to upgrade from 8.3 to 8.4 on the same server and avoid having the 
significant downtime of dump/restore?

If so, I understand the two servers would have to run on different 
ports.  Are there any other issues/traps to be aware of?

-- 

Thank you,

Lewis Kapell
Computer Operations
Seton Home Study School


</PRE>
<BR>
</BODY>
</HTML>

--=-USLgDqw5mJxj4bnEfstK--