From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Thom Brown <thombrown(at)gmail(dot)com> |
Cc: | Chris Barnes <compuguruchrisbarnes(at)hotmail(dot)com>, Postgres General Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Postgres wal shipping from 8.33 to 8.42. |
Date: | 2010-02-04 16:12:14 |
Message-ID: | dcc563d11002040812k67fb6246o7d9cdc76090e8df8@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Feb 4, 2010 at 8:58 AM, Thom Brown <thombrown(at)gmail(dot)com> wrote:
> On 4 February 2010 15:54, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
>> On Thu, Feb 4, 2010 at 7:54 AM, Chris Barnes
>> <compuguruchrisbarnes(at)hotmail(dot)com> wrote:
>>> We are trying to minimize our downtime in production to upgrade from 8.33 to
>>> 8.42.
>>>
>>> What we would like to be able to do is this:
>>> Upgrade the slave we are currently shipping to, to version 8.4.2. Continue
>>> to pitr to this server. And switch over and then upgrade the master.
>>>
>>> My question is, will pitr wal logs ship and be processed from a machine
>>> running 8.33 to 8.42.
>>
>> Nope. But you can use slony to upgrade.
>>
>
> Or pg_migrator? http://pgfoundry.org/projects/pg-migrator
For minimal downtime, slony would win, but for reducing effort,
pg_migrator wins.
From | Date | Subject | |
---|---|---|---|
Next Message | Wang, Mary Y | 2010-02-04 16:28:22 | Any Good Postgresql Courses Offered in the US Area? |
Previous Message | Thom Brown | 2010-02-04 16:08:37 | Re: Performance Tuning - Any easy things that I can do ? |