Details

    • Bug
    • Status: Closed (View Workflow)
    • Trivial
    • Resolution: Fixed
    • 10.4(EOL)
    • N/A
    • Documentation
    • None

    Description

      Hi,

      • HELP ANALYZE TABLE
      • KB ANALYZE TABLE
        Don't talks about PERSISTENT keyword but EITS became default in 10.4

      Attachments

        Issue Links

          Activity

            greenman Ian Gilfillan added a comment -

            HELP is part of by MDEV-6521, which will be automatically generated from the KB. For the second part, are you talking about the page https://mariadb.com/kb/en/library/analyze-table/? This needs updating, but does mention the PERSISTENT keyword. If there's another page, please link it here.

            greenman Ian Gilfillan added a comment - HELP is part of by MDEV-6521 , which will be automatically generated from the KB. For the second part, are you talking about the page https://mariadb.com/kb/en/library/analyze-table/? This needs updating, but does mention the PERSISTENT keyword. If there's another page, please link it here.

            Hi Ian i open that issue during the pick hit in europe , may be i miss read the KB or may be google point to some old page , please apology for wrong reporting looks like KB is indeed correct

            stephane@skysql.com VAROQUI Stephane added a comment - Hi Ian i open that issue during the pick hit in europe , may be i miss read the KB or may be google point to some old page , please apology for wrong reporting looks like KB is indeed correct

            At the same time i think review is needed : "For InnoDB the table is locked with a write lock." this statement need to be refresh to relate the last status of innodb locking on analyze , i was told this was changed long time ago to be non locking, if still locking spending so much effort on instant DDL operation and keeping an analyze under lock would be very sad !

            stephane@skysql.com VAROQUI Stephane added a comment - At the same time i think review is needed : "For InnoDB the table is locked with a write lock." this statement need to be refresh to relate the last status of innodb locking on analyze , i was told this was changed long time ago to be non locking, if still locking spending so much effort on instant DDL operation and keeping an analyze under lock would be very sad !

            People

              greenman Ian Gilfillan
              stephane@skysql.com VAROQUI Stephane
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

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