Hi, Kristian!
On Sep 03, Kristian Nielsen wrote:
>
> >> - If we have consistent commit order, we can think about
> >> optimising commit to need only one fsync (for binlog); lost
> >> commits in storage engines can then be recovered from the binlog
> >> at crash recovery by re-playing against
---
WORKLOG TASK
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
TASK...: Cross-engine consistency for START TRANSACTION WITH CONSISTENT
SNAPSHOT
CREATION DATE..: Fri,
Sergei Golubchik writes:
> Hi, Kristian!
>
> Let's start from the WL description:
Thanks for your detailed comments!
>> While currently there is no server guarantee to get same commit order
>> in engines an binlog (except for the InnoDB prepare_commit_mutex
>> hack), there are several reasons w
3 matches
Mail list logo