On Sat, Jun 20, 2009 at 11:16 AM, Robert
Hodges<robert.hodges@continuent.com> wrote:
> Hi All,
>
> I have the same question as Mark, namely:  what is the prioritized list of
> possible improvements to replication?  To answer Mark's other question,
> improving replication is work that we (Continuent) would be willing to help
> fund.  Improvements in this area seem like a great way for MariaDB to
> differentiate itself.  We would like to help create the list of likely areas
> for improvement both in terms of benefits to users as well as how feasible
> fixes are.
>
> Here are a few items that I have run into during work in the MySQL binlog.
> They may be different from other people as we are parsing the binlog
> directly,  which is not something that the average user does regularly.
>
> * Event checksums.  Binlog corruption does not happen too often but it's bad
> when it does.  I got it last week during a customer demo.  :(
>
> * Column names in table map events.  Right now it's just numbers.  Not good
> for filtering SQL or replication to other databases.
>
> * Keys.  Update events in row replication use before/after images but do not
> specify keys.  This is problematic in a number of cases.
>
> Global transaction IDs and semi-synchronous replication support would also
> be high on my list of feature additions for general usability.  Fixes for
> serious bugs would also be very welcome.
>
> Cheers, Robert
>
> P.s., Mark, do you have a pointer to the extensibility bug(s)?

Justin or Mats might know the bug numbers. The fix for this should be
included in the launchpad branch Justin created for global group ids
-- https://code.launchpad.net/~jtolmer/mysql-server/global-trx-ids 

--
Mark Callaghan
mdcallag@gmail.com