OK, that is what I wanted to know.
On Wed, Apr 6, 2011 at 6:16 AM, Kristian Nielsen
wrote:
> MARK CALLAGHAN writes:
>
>> Is commit_ordered called before or after the transaction's XID event
>> has been written to the binlog?
>> after it has been forced (fsync) to the binlog?
>
> It is called
MARK CALLAGHAN writes:
> Is commit_ordered called before or after the transaction's XID event
> has been written to the binlog?
> after it has been forced (fsync) to the binlog?
It is called just after XID event has been written (and fsync()ed in case of
sync_binlog=1) to binlog.
- Kristia
Is commit_ordered called before or after the transaction's XID event
has been written to the binlog?
after it has been forced (fsync) to the binlog?
On Wed, Apr 6, 2011 at 12:16 AM, Kristian Nielsen
wrote:
> Hi Serg,
>
> As promised, here is a summary of the changes to the storage engine API
Hi, Kristian!
On Apr 06, Kristian Nielsen wrote:
>
> As promised, here is a summary of the changes to the storage engine
> API that I made as part of group commit.
>
> Two new handlerton methods are added:
>
> void (*prepare_ordered)(handlerton *hton, THD *thd, bool all);
> void (*commi
Hi Serg,
As promised, here is a summary of the changes to the storage engine API that I
made as part of group commit.
Two new handlerton methods are added:
void (*prepare_ordered)(handlerton *hton, THD *thd, bool all);
void (*commit_ordered)(handlerton *hton, THD *thd, bool all);
commit
5 matches
Mail list logo
