-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Andrew,

I made sure that what I was adding to the set was an *empty* table not
being updated by whatever... (yet) :)

BR,

Pedro Doria Meunier
GSM: +351 96 17 20 188
Skype: pdoriam
 



Andrew Sullivan wrote:
> On Fri, Jul 03, 2009 at 12:06:49PM +0100, Pedro Doria Meunier
> wrote:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>>
>> Hi Andrew,
>>
>> This bit: http://www.slony.info/documentation/stmtmergeset.html
>
> Oh, I see what you mean: you used the _same set_ and added tables
> to it.  Hrm.  I see no evidence in the release notes that it
> changed. Are you sure it's actually working?  In particular, the
> reason this is supposed to fail is because of a bootstrap problem
> in which you can't be sure that the tables are available everywhere
> before data shows up in the first table.  This can result in
> bizarre race-condition failures.  So it's not supposed to be
> allowed.  But note that I'm out of touch on the tip of Slony
> development, since I don't actively use it anywhere.  Maybe this
> has been worked around.
>
> A
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFKThO22FH5GXCfxAsRAk3GAJwLHOknSOV3flY+zA6bnz8kPXLnDgCgjRTZ
3X3Vu6LGrDHAHb6oimqFpec=
=6BJV
-----END PGP SIGNATURE-----