INNODB_BUFFER_POOL_PAGES_BLOB stores incorrect NEXT_PAGE_NO

Bug #1056586 reported by Laurynas Biveinis
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Status tracked in 5.7
5.1
Won't Fix
Medium
Unassigned
5.5
Triaged
Medium
Unassigned
5.6
Invalid
Undecided
Unassigned
5.7
Invalid
Undecided
Unassigned

Bug Description

The code in i_s_innodb_buffer_pool_pages_blob_fill() reads:

next_page_no = ... read read read ... ;
...
table->field[1]->store(block->page.offset);
...
if(next_page_no == FIL_NULL)
{
  table->field[4]->store(0);
} else {
  table->field[4]->store(block->page.offset); <- oops!
}

Also, the tests for this table are terribly inadequate (percona_skip_innodb_i_s.test)

tags: added: xtradb
tags: added: low-hanging-fruit
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-2805

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.