From: | Iñigo Martinez Lasala <imartinez(at)vectorsf(dot)com> |
---|---|
To: | Brad Nicholson <bnichols(at)ca(dot)afilias(dot)info> |
Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Migrate postgres to newer hardware |
Date: | 2010-04-02 07:41:09 |
Message-ID: | 1270194070.7497.1.camel@deimos |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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(at)ca(dot)afilias(dot)info>
To: Iñigo Martinez Lasala <imartinez(at)vectorsf(dot)com>
Cc: Renato Oliveira <renato(dot)oliveira(at)grant(dot)co(dot)uk>, pgsql-admin
<pgsql-admin(at)postgresql(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | scheu dba | 2010-04-02 07:48:23 | dblink_connect is slow |
Previous Message | Gnanakumar | 2010-04-02 06:35:03 | Database clone stuck in the middle |