Hi!

On Oct 10, 2008, at 7:02 PM, MARK CALLAGHAN wrote:

Some of the work in progress might be interesting to others. We have
implemented binlog event checksums, global transaction IDs and a few

I am seriously unhappy with the 5.1 replication changes. Knowing that they have rolled back to just doing statement in the server has meant to me that there is no faith in the row code working. At this point I am tempted to just kick out the binlog and rewrite it while taking the touch points for row and putting in a new set of calls for it. For the moment leave the transport protocol alone.

extend the use of internal XA transactions to keep the SQL slave
thread and storage engines in sync as an alternative to our current
use hidden variables in the InnoDB tx log.

Are you concerned with supporting multiple engines?

Where in the land of drizzle branches is the change to clean up the
net send/receive code so it uses blocking  calls with timeouts rather
than setsockopt(non blocking), try call, setsockopt(blocking), request
a timeout alarm from another thread, do blocking call, ...? If you
have it, I want to copy it.

We do, but you would need to look at our patch history. It would be simpler to just have me show you were to remove the code from then try to take a patch. Will you be at the opensql camp?

Cheers,
        -Brian




Cheers,
      -Brian

--
_______________________________________________________
Brian "Krow" Aker, brian at tangent.org
Seattle, Washington
http://krow.net/                     <-- Me
http://tangent.org/                <-- Software
_______________________________________________________
You can't grep a dead tree.







--
Mark Callaghan
[EMAIL PROTECTED]

--
_______________________________________________________
Brian "Krow" Aker, brian at tangent.org
Seattle, Washington
http://krow.net/                     <-- Me
http://tangent.org/                <-- Software
_______________________________________________________
You can't grep a dead tree.




_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help   : https://help.launchpad.net/ListHelp

Reply via email to