Postgres Pro
Downloads
Home   >   mailing lists

Strategy for moving a large DB to another machine with least possible down-time - Mailing list pgsql-general

From Andreas Joseph Krogh
Subject Strategy for moving a large DB to another machine with least possible down-time
Date
Msg-id VisenaEmail.57.45219778166c5146.14897f82eab@tc7-visena
Whole thread Raw
Responses Re: Strategy for moving a large DB to another machine with least possible down-time  (Bill Moran <wmoran@potentialtech.com>)
Re: Strategy for moving a large DB to another machine with least possible down-time  (Andy Colson <andy@squeakycode.net>)
List pgsql-general
Tree view
Hi all.
 
PG-version: 9.3.5
 
I have a DB large enough for it to be impractical to pg_dump/restore it (would require too much down-time for customer). Note that I'm noe able to move the whole cluster, only *one* DB in that cluster.
 
What is the best way to perform such a move, can i use PITR, rsync + webl-replay magic, what else?
Can Barman help with this, maybe?
 
Thanks.
 
--
Andreas Joseph Krogh
CTO / Partner - Visena AS
Mobile: +47 909 56 963
Attachment

pgsql-general by date:

Previous
From: David G Johnston
Date:
Subject: Re: cloning database
Next
From: Bill Moran
Date:
Subject: Re: Strategy for moving a large DB to another machine with least possible down-time