Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-5400

Make dump options in wt verify consistent

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • Backlog
    • Affects Version/s: None
    • Component/s: None
    • Storage Engines 2020-01-27

      Follow-up from WT-5345.

      Providing multiple configuration options to wt verify causes the output to be messy - with duplicate information printed and inconsistent formatting. See the following example of -d dump_address -d dump_pages

      file:ts05.wt: checkpoint WiredTigerCheckpoint.1
      Root: [8192-12288, 4096, 470927008] row-store internal
      row-store internal
      [Root]
      0x1a51868: row-store internal
      disk 0x1a5d290, dsk_mem_size 53, entries 1, clean, disk-alloc, memory-size 317
      K {\00}
      0x1a530c0 disk [4096-8192, 4096, 3077701246]
      row-store leaf
      [4096-8192, 4096, 3077701246]
      0x1a530c0: row-store leaf
      disk 0x1a5e2a0, dsk_mem_size 58, entries 1, clean, disk-alloc, memory-size 146
      K {200}
      V {new value} 

      This is caused by the flags delegating printing using different _debug functions which dump information in their own format. Printing should be made consistent.

            Assignee:
            jeremy.tay@mongodb.com Jeremy Tay (Inactive)
            Reporter:
            jeremy.tay@mongodb.com Jeremy Tay (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: