| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Allan Kamau <kamauallan(at)gmail(dot)com> |
| Cc: | Postgres General Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: PG migration policy |
| Date: | 2012-01-29 18:09:41 |
| Message-ID: | CAOR=d=0+fXCUXjkZb8PFfs9mHA3VxxUHrs2m3o2pjRS8gMsQ8w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sat, Jan 28, 2012 at 11:30 PM, Allan Kamau <kamauallan(at)gmail(dot)com> wrote:
> Hi,
> This is definitely off topic, I apologize.
> We are planning to move our PostgreSQL installation from a shared
> server to a dedicated server. I have been given the responsibility of
> writing a migration policy document for this operation. This would be
> my first such document to put together,
> I am looking for pointers, samples and so on on which to build this
> document for our scenario.
Assuming you've tested ahead of time, the real question is how much
down time can you afford?
If you can afford hours or more of downtime, a dump and restore if the
easiest way.
If you need to keep your down time to a minimum, then look at using
some form of replication and switching from master to slave once the
slave is caught up.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2012-01-29 19:01:16 | Re: PG migration policy |
| Previous Message | Andy Colson | 2012-01-29 14:58:52 | Re: PG migration policy |