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

connect_work_size written in connect.cnf is false

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Cannot Reproduce
    • 10.0.13
    • 10.0.14
    • None
    • CentOS release 6.5 (X86_64)

    Description

      I installed Microsoft ODBC Driver 11 for SQL Server with unixODBC2.3.0.

      I am trying to insert into a connect table (SQL Server2005 table in another server) and found that connect_work_size is not set properly when written in connect.cnf.

      When I write inside connect.cnf below,

      connect_work_size=512M

      I get the following error in /var/lib/mysql/servername.err

      PlugSubAlloc: Not enough memory in Work area for request of 80 (used=67108792 free=72)

      The size used+free is 64M, whcih is the default connect_work_size.
      Not the size set in connect.cnf.

      Although in Maria I get the following,

      show variables like 'connect_work_size';
      +-------------------+-----------+
      | Variable_name     | Value     |
      +-------------------+-----------+
      | connect_work_size | 536870912 |
      +-------------------+-----------+
      1 row in set (0.00 sec)

      When I set in Maria using the command,

      set global connect_work_size=536870912;

      the error changes to a correct one as below.

      PlugSubAlloc: Not enough memory in Work area for request of 40 (used=536870888 free=24)

      Attachments

        Issue Links

          Activity

            People

              bertrandop Olivier Bertrand
              takuya Takuya Aoki (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              3 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.