Hi Laurynas,
On Wed, May 6, 2015 at 9:14 PM, Laurynas Biveinis <
laurynas.bivei...@gmail.com> wrote:
> Xiaofei -
>
> > Does InnoDB maintain a dirty
> > page table?
>
> You must be referring to the buffer pool flush_list.
>
You are right. The flush_list is can be used for recovery and checkpoint.
Hi Jan,
The only place fsync is called after AIO that I could find is in
function buf_LRU_remove_pages
(buf0lru.cc)
But after other AIO operations, I didn't see fsync is called.
Do you know how this difference will affect the recovery process? Thanks.
Xiaofei
On Wed, May 6, 2015 at 8:24 PM, Jan
Xiaofei -
> Does InnoDB maintain a dirty
> page table?
You must be referring to the buffer pool flush_list.
> Is fsync called to guarantee the page to be on persistent
> storage so that the dirty page table can be updated? If this is the case,
> when is the dirty page table updated for asynchron
Hi Jan,
Thanks for clarification. I should have used synchronous write, instead of
synchronous flush. My point is that I noticed for sync writes, fsync is
called to force pages to be on persistent storage. while for AIO pages,
fsync is not called to force pages to be on persistent storage. My ques
4 matches
Mail list logo
