On Wed, Jul 1, 2009 at 12:11 PM, "Stéphane A.
Schildknecht"<stephane.schildknecht@postgresqlfr.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Scott Marlowe a écrit :
>> On Wed, Jul 1, 2009 at 11:57 AM, "Stéphane A.
>> Schildknecht"<stephane.schildknecht@postgresqlfr.org> wrote:
>>> Problem yet is I can't use slony any more to replicate data, as it falls in
>>
>>> I'm quit disappointed, as if I let slony replicate the application, still in a
>>> process of migration to 8.3 correct behaviour can't be used, on the other hand
>>> if I add implicit casts to allow application to work, I can't replicate with slony.
>>
>> So, is fixing the app an option?
>>
>
> Definitely not... as it would last too long to be an option.
> It surely is a long-term option. And it needs to be done, but not yet.
So, can you keep up x numbers of slony reps running 8.2 that only the
app can see, replicate to an 8.3 that doesn't get hit by the user,
then switch to the new 8.3 instance(s) and apply the gruesome
auto-cast to the 8.3 afterwards, and then slony will work between two
patched 8.3 instances? Just a SWAG, I'm not there to test it or
anything.
