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

SET STATEMENT query_cache_type apparently has no effect and hence should be disallowed

    XMLWordPrintable

    Details

      Description

      From all I see, SET STATEMENT ... FOR SELECT queries are not put in the query cache and do not use it, whatever parameters are.

      Then, SET STATEMENT query_cache_type = ... can't have any effect, and thus should be disabled with ER_SET_STATEMENT_NOT_SUPPORTED. Same is probably true for other query_cache_* variables potentially changeable in SET STATEMENT context (query_cache_strip_comments? query_cache_wlock_invalidate?).

      In Percona server it looks even worse, SET STATEMENT .. queries are put into the query cache, but never hit it.

        Attachments

          Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-8185 Variables related to query cache are useless in SET STATEMENT

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open

          Task - A task that needs to be done. MDEV-5231 Per query variables from Percona Server [patch]

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

          Technical task - A technical task. MDEV-6923 Testing for SET STATEMENT .. FOR (MDEV-5231, per-query variables)

          • Major - Major loss of function.
          • Closed
          links to

          Web Link Bug#1387273 - SET STATEMENT queries are put into query cache but never hit it

            Activity

              People

              Assignee:
              sanja Oleksandr Byelkin
              Reporter:
              elenst Elena Stepanova
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Git Integration