Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-33943

Query_log_event thread_id only writes first 4 bytes

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.5, 10.6, 10.11, 11.1(EOL), 11.2, 11.4, 11.0(EOL), 11.3(EOL)
    • 10.5, 10.6, 10.11, 11.2, 11.4
    • Replication
    • None

    Description

      The thread_id type is 8 bytes long, but only the first 4 are stored when the event is written into the binlog. The event should be extended to write the remaining 4 bytes of the thread_id in a separate piece of the event, which can be combined together when parsed.

      Attachments

        Issue Links

          relates to

          New Feature - A new feature of the product, which has yet to be developed. MDEV-7850 Extend GTID Binlog Events with Thread Id

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-33924 Gtid_log_event thread_id missing in binlog when pseudo_thread_id is set to 0 or negative

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Activity

            People

              bnestere Brandon Nesterenko
              bnestere Brandon Nesterenko
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.