From: | decibel <decibel(at)decibel(dot)org> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
Subject: | Re: Streaming Rep - 2-phase backups and reducing time to full replication |
Date: | 2009-12-22 21:33:16 |
Message-ID: | 6F7E417A-A9A6-4542-88B2-A47F81900E8E@decibel.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Dec 22, 2009, at 12:54 PM, Simon Riggs wrote:
> 9. Create a recovery command file in the standby server with parameters
> required for streaming replication.
>
> 7. (a) Make a base backup of minimal essential files from primary
> server, load this data onto the standby.
>
> 10. Start postgres in the standby server. It will start streaming
> replication.
>
> 7. (b) Continue with second phase of base backup, copying all remaining
> files, ending with pg_stop_backup()
Dumb question: could the WAL streaming code be made to also ship base files? That would make setting up a streaming replica super-simple.
--
Jim C. Nasby, Database Architect jim(at)nasby(dot)net
512.569.9461 (cell) http://jim.nasby.net
From | Date | Subject | |
---|---|---|---|
Next Message | decibel | 2009-12-22 22:04:15 | Re: Removing pg_migrator limitations |
Previous Message | Aidan Van Dyk | 2009-12-22 21:17:15 | Re: Backup history file should be replicated in Streaming Replication? |