From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Andrew Hannon <ahannon(at)fiksu(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Two 9.1 Questions |
Date: | 2011-09-12 16:19:12 |
Message-ID: | CA+U5nMJV3MaAFsgaAdSdnjzdrqj2T6w-eyC2hpBqm1OyYp7MDQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Sep 12, 2011 at 4:52 PM, Andrew Hannon <ahannon(at)fiksu(dot)com> wrote:
> Hello,
>
> Now that 9.1 has been released, I have two questions:
>
> 1. Can we upgrade a 9.0 hot standby (replicating from a 9.0 master) to a 9.1 standby while still replicating from the 9.0 master? Are there any version differences that would cause a problem? We would then eventually promote the 9.1 machine to the master...
Not yet. That's a planned feature awaiting funding.
> 2. Is it possible to do something like the following:
> A. Pause Replication on a hot standby (using the pause_at_recovery_target recovery target setting)
> B. Call pg_dumpall on the slave
> C. Resume replication (by disabling the pause_at_recovery_target recovery target setting)
>
> During the pause, we would likely continue shipping WAL to the slave (unless this is unadvisable).
>
> Is this a reasonable approach?
It will work... please read about the functions for pause/resume.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Grzegorz Jaśkiewicz | 2011-09-12 16:32:03 | Re: 8.4.4 locked after power failure |
Previous Message | Andrew Hannon | 2011-09-12 15:52:37 | Two 9.1 Questions |