On Thu, Feb 4, 2010 at 8:58 AM, Thom Brown wrote:
> On 4 February 2010 15:54, Scott Marlowe wrote:
>> On Thu, Feb 4, 2010 at 7:54 AM, Chris Barnes
>> 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 t
On 4 February 2010 15:54, Scott Marlowe wrote:
> On Thu, Feb 4, 2010 at 7:54 AM, Chris Barnes
> 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
On Thu, Feb 4, 2010 at 7:54 AM, Chris Barnes
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 swi
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 upg
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,
