Postgres Pro
Downloads
Home   >   mailing lists

Thread: Postgres wal shipping from 8.33 to 8.42.

Postgres wal shipping from 8.33 to 8.42.

From
Chris Barnes
Date:
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.
 
Any thoughts on this would be appreciated.
 
Thanks,
 
Chris

Re: Postgres wal shipping from 8.33 to 8.42.

From
"A. Kretschmer"
Date:
In response to Chris Barnes :
> 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.

No.


Regards, Andreas
--
Andreas Kretschmer
Kontakt:  Heynitz: 035242/47150,   D1: 0160/7141639 (mehr: -> Header)
GnuPG: 0x31720C99, 1006 CCB4 A326 1D42 6431  2EB0 389D 1DC2 3172 0C99

Re: Postgres wal shipping from 8.33 to 8.42.

From
Scott Marlowe
Date:
On Thu, Feb 4, 2010 at 7:54 AM, Chris Barnes
<compuguruchrisbarnes@hotmail.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.

Re: Postgres wal shipping from 8.33 to 8.42.

From
Thom Brown
Date:
On 4 February 2010 15:54, Scott Marlowe <scott.marlowe@gmail.com> wrote:
> On Thu, Feb 4, 2010 at 7:54 AM, Chris Barnes
> <compuguruchrisbarnes@hotmail.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

Thom

Re: Postgres wal shipping from 8.33 to 8.42.

From
Scott Marlowe
Date:
On Thu, Feb 4, 2010 at 8:58 AM, Thom Brown <thombrown@gmail.com> wrote:
> On 4 February 2010 15:54, Scott Marlowe <scott.marlowe@gmail.com> wrote:
>> On Thu, Feb 4, 2010 at 7:54 AM, Chris Barnes
>> <compuguruchrisbarnes@hotmail.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.