| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | "<pgsql-hackers(at)postgresql(dot)org>" <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | David Jantzen <djantzen(at)ql2(dot)com> |
| Subject: | Re: Fwd: Reversing flow of WAL shipping |
| Date: | 2009-10-22 18:20:09 |
| Message-ID: | 407d949e0910221120w141a458l809b54d8250432e2@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-general pgsql-hackers |
[moving to pgsql-hackers]
On Thu, Oct 22, 2009 at 10:28 AM, 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?
This is definitely something that needs to be addressed in future
versions of Postgres, especially once we have Hot
Standby/Read-Only-Slaves and Sync-Replication. People will want to
have dozens of active slaves and rebuilding them all every time a
failover happens will be unbearable. Not to mention that in the
meantime they have to live with no redundancy.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Eric Comeau | 2009-10-22 18:29:47 | Increasing the length of a VARCHAR column without table rewrite |
| Previous Message | Kevin Grittner | 2009-10-22 17:41:59 | Re: Fwd: Reversing flow of WAL shipping |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Viktor Rosenfeld | 2009-10-22 18:24:34 | Getting rid of UNION |
| Previous Message | Kevin Grittner | 2009-10-22 17:41:59 | Re: Fwd: Reversing flow of WAL shipping |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2009-10-22 18:28:44 | Re: per table random-page-cost? |
| Previous Message | Tom Lane | 2009-10-22 18:12:16 | Re: EvalPlanQual seems a tad broken |