Received: from maia.hub.org (unknown [200.46.208.211])
	by mail.postgresql.org (Postfix) with ESMTP id D6EDF6338AA
	for <pgsql-admin-postgresql.org@mail.postgresql.org>;
	Fri,  2 Apr 2010 04:41:31 -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 25724-03 for
	<pgsql-admin-postgresql.org@mail.postgresql.org>;
	Fri,  2 Apr 2010 07:41:17 +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 C282F632D35
	for <pgsql-admin@postgresql.org>; Fri,  2 Apr 2010 04:41:20 -0300 (ADT)
Received: from localhost (localhost.localdomain [127.0.0.1])
	by hermes.vectorsf.com (Postfix) with ESMTP id F2A9924800A3;
	Fri,  2 Apr 2010 09:41:16 +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 va1ZMrGGY4M6; Fri,  2 Apr 2010 09:41:13 +0200 (CEST)
Received: from [90.168.224.67] (unknown [90.168.224.67])
	(Authenticated sender: imartinez)
	by hermes.vectorsf.com (Postfix) with ESMTP id 9A21924800A2;
	Fri,  2 Apr 2010 09:41:11 +0200 (CEST)
Subject: Re: Migrate postgres to newer hardware
From: =?ISO-8859-1?Q?I=F1igo?= Martinez Lasala <imartinez@vectorsf.com>
To: Brad Nicholson <bnichols@ca.afilias.info>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
In-Reply-To: <1269959882.5155.145.camel@bnicholson-desktop>
References: <7965A9DCF12CC14984420BCC37B1608F25AB1AED49@Elzar.grant.co.uk>
	<1269959369.15416.5.camel@deimos>
	<1269959882.5155.145.camel@bnicholson-desktop>
Content-Type: multipart/alternative; boundary="=-/CqdAX5qBwmo0KX7Wudq"
Date: Fri, 02 Apr 2010 09:41:09 +0200
Message-ID: <1270194070.7497.1.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=-1.109 tagged_above=-10 required=5
	tests=BAYES_05=-1.11, HTML_MESSAGE=0.001
X-Spam-Level: 
X-Archive-Number: 201004/8
X-Sequence-Number: 34102


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

I would never sing a SLA for HA if I don't have system, at least, fully
redundant in order to deal with these issues.
Single server, single point of failure.

-----Original Message-----
From: Brad Nicholson <bnichols@ca.afilias.info>
To: Iñigo Martinez Lasala <imartinez@vectorsf.com>
Cc: Renato Oliveira <renato.oliveira@grant.co.uk>, pgsql-admin
<pgsql-admin@postgresql.org>
Subject: Re: [ADMIN] Migrate postgres to newer hardware
Date: Tue, 30 Mar 2010 10:38:02 -0400


On Tue, 2010-03-30 at 16:29 +0200, Iñigo Martinez Lasala wrote:
> Hi Renato.
> 
> I would follow the ancient method: perform a pg_dump / pg_restore

This is the easiest approach.  The problem is that a lot of people have
contractual SLA's that do not allow them to take their systems down long
enough to do a dump and restore upgrade.




--=-/CqdAX5qBwmo0KX7Wudq
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>
I would never sing a SLA for HA if I don't have system, at least, fully redundant in order to deal with these issues.<BR>
Single server, single point of failure.<BR>
<BR>
-----Original Message-----<BR>
<B>From</B>: Brad Nicholson &lt;<A HREF="mailto:Brad%20Nicholson%20%3cbnichols@ca.afilias.info%3e">bnichols@ca.afilias.info</A>&gt;<BR>
<B>To</B>: I&#241;igo Martinez Lasala &lt;<A HREF="mailto:%3d%3fISO-8859-1%3fQ%3fI%3dF1igo%3f%3d%20Martinez%20Lasala%20%3cimartinez@vectorsf.com%3e">imartinez@vectorsf.com</A>&gt;<BR>
<B>Cc</B>: Renato Oliveira &lt;<A HREF="mailto:Renato%20Oliveira%20%3crenato.oliveira@grant.co.uk%3e">renato.oliveira@grant.co.uk</A>&gt;, pgsql-admin &lt;<A HREF="mailto:pgsql-admin%20%3cpgsql-admin@postgresql.org%3e">pgsql-admin@postgresql.org</A>&gt;<BR>
<B>Subject</B>: Re: [ADMIN] Migrate postgres to newer hardware<BR>
<B>Date</B>: Tue, 30 Mar 2010 10:38:02 -0400<BR>
<BR>
<PRE>
On Tue, 2010-03-30 at 16:29 +0200, I&#241;igo Martinez Lasala wrote:
&gt; Hi Renato.
&gt; 
&gt; I would follow the ancient method: perform a pg_dump / pg_restore

This is the easiest approach.  The problem is that a lot of people have
contractual SLA's that do not allow them to take their systems down long
enough to do a dump and restore upgrade.

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

--=-/CqdAX5qBwmo0KX7Wudq--