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

Fix prepared transaction assert always messages

    • Storage Engines
    • 2
    • 2024-07-23 - Mining crypto

      The second of these two assert always messages:

                      WT_ASSERT_ALWAYS(session,
                        F_ISSET(r, WT_REC_EVICT) ||
                          (F_ISSET(r, WT_REC_VISIBILITY_ERR) &&
                            F_ISSET(upd, WT_UPDATE_PREPARE_RESTORED_FROM_DS)),
                        "rec_upd_select found an in-progress prepared update");
                      WT_ASSERT_ALWAYS(session, upd->prepare_state == WT_PREPARE_INPROGRESS,
                        "rec_upd_select found an in-progress prepared update");
       

      Tells the user what the passing condition is for the assertion, it should tell the user what the failing reason is.

      Additional the first message is the same as the second however the conditions required to trigger it are very different.

      Scope:

      • Fix the messages

            Assignee:
            chenhao.qu@mongodb.com Chenhao Qu
            Reporter:
            luke.pearson@mongodb.com Luke Pearson
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: