innodb_flush_log_at_trx_commit - per thread

Registered by Vadim Tkachenko

From Peter:

I was wondering if we can make it so this variable is per thread ( can be set by super user)

This would allow to run some of transactions which do not need durability while others which are durable.
I often see such things when say only 10% of operations really need to be durable while we get the hit on everything.

The use case is mainly when there are a lot of non-durable operations and some durable, something like

NNNNDNNNNNDNNNND

The durable transactions will need to flush the complete log (but it will contain no more than 1 second of changes anyway).

While log is being synced by Durable transaction I assume non durable will be just written to the log buffer - it is my understanding only when transaction log is synced you need to wait on the previous log sync completion.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
Vadim Tkachenko
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Implemented
Milestone target:
milestone icon 5.1-12.0
Started by
Yasufumi Kinoshita
Completed by
Alexey Kopytov

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.