On Mon, Mar 3, 2014 at 9:44 AM, Kevin Harriss <[email protected]> wrote: > I need to move the wal-e bucket to a different S3 account. Are there any > known problems with migrating a working postgres streaming replication > master slave setup to a new S3 bucket? It seems that the following steps > would be all that is needed to be done to migrate to a new S3 bucket. > > - Change wal-e settings on master > - Push backup with wal-e from master > - Stop the slave > - Delete current data dir > - Do a fresh wal-e fetch
You can do this, or you can try to re-point the slave, by changing its configuration after it has replayed all WAL in the original location. But a fresh fetch may be less effortful and error-prone. I do have ambitions for the not-even-remotely-started v0.8 release to support stitching together multiple eras of the WAL being uploaded. It'll be quite a bit of churn to the way configuration is done, but I think it is for the best. -- You received this message because you are subscribed to the Google Groups "wal-e" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
