Uploaded image for project: 'MariaDB MaxScale'
  1. MariaDB MaxScale
  2. MXS-7576

Query against Exasol hangs when the result set has a large VARCHAR and a TIMESTAMP

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 25.10
    • 26.10.0
    • Core
    • None
    • MXS-SPRINT-279
    • Can result in hang or crash
    • Hide
      A query against Exasol hanged MaxScale when the result set contained both a very large VARCHAR and a TIMESTAMP. The large VARCHAR disables batching, so rows are fetched column by column and the TIMESTAMP then truncates because the driver returns more characters than it declared. That caused MaxScale to enter an endless loop. Now, TIMESTAMPs even if the driver returns more characters that it claims to do.
      Show
      A query against Exasol hanged MaxScale when the result set contained both a very large VARCHAR and a TIMESTAMP. The large VARCHAR disables batching, so rows are fetched column by column and the TIMESTAMP then truncates because the driver returns more characters than it declared. That caused MaxScale to enter an endless loop. Now, TIMESTAMPs even if the driver returns more characters that it claims to do.

    Description

      A query against Exasol hangs MaxScale when the result set contains both a very large VARCHAR and a TIMESTAMP. The large VARCHAR disables batching, so rows are fetched column by column with SQLGetData, and the TIMESTAMP then truncates because the driver returns more characters than it declared. The retry loop in mxq::ODBC::get_normal_result() resizes the buffer to exactly the indicator value, leaving no room for the terminating NUL, so the driver truncates again and reports the same indicator. Nothing changes between iterations and the loop spins forever inside a driver call that holds a driver-internal mutex.

      Attachments

        Issue Links

          Activity

            People

              johan.wikman Johan Wikman
              johan.wikman Johan Wikman
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 0.5d
                  0.5d
                  Remaining:
                  Remaining Estimate - 0d
                  0d
                  Logged:
                  Time Spent - 0.5d
                  0.5d

                  Git Integration

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