| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "jd(at)commandprompt(dot)com" <jd(at)commandprompt(dot)com>, "David Jantzen" <djantzen(at)ql2(dot)com> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Fwd: Reversing flow of WAL shipping |
| Date: | 2009-10-22 17:41:59 |
| Message-ID: | 4AE05317020000250002BDE8@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general pgsql-hackers |
David Jantzen <djantzen(at)ql2(dot)com> wrote:
> Thanks for the quick response Joshua, much appreciated. Is there
> any way to avoid or minimize a period without a warm standby when I
> switch to Server B for production? What about rsyncing the data
> directory from Server B to Server C after B goes live?
In my experience, proper use of rsync just before the switch, combined
with use of rsync as your PITR base backup technique, can make for a
very short period without warm standby.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2009-10-22 18:20:09 | Re: Fwd: Reversing flow of WAL shipping |
| Previous Message | Scott Mead | 2009-10-22 17:36:58 | Re: Fwd: Reversing flow of WAL shipping |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2009-10-22 18:20:09 | Re: Fwd: Reversing flow of WAL shipping |
| Previous Message | Scott Mead | 2009-10-22 17:36:58 | Re: Fwd: Reversing flow of WAL shipping |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2009-10-22 17:43:36 | Re: B-tree leaf node structure |
| Previous Message | Scott Mead | 2009-10-22 17:36:58 | Re: Fwd: Reversing flow of WAL shipping |