Mark Little wrote:
Yes, slightly. I think there was a misunderstanding between parties then at least as timing goes, because the TS team were alreadly planning for 6.1.
That's fantastic news then. My comment was in reaction to an email from Jonathan that all new work most go into TS 5, which would be incompatible with 6.0 (and also that the planning cycle for 5 is basically over). So I can take this to mean there will definitely be a 4.16 which will address discovered EAP 6.x issues such as this?
My biggest concern has always been pushing something into the release that's not fully tested.
Yeah I certainly understand the concern here but to a certain extent we have to pick a lesser evil. My understanding (feel free to correct), is that XATerminator when used with 4.15 may be unable to enlist more than one resource without detrimental side effects. It does seem though that even with 4.15 there are some pretty powerful SPIs we might be able to use for a stop-gap solution (perhaps some kind of bqual xid manipulation can be done there?) This does make me wonder, that even conceeding the API is inadequate, what other XATerminator implementations do to handle this issue.