[MDEV-30411] main.explain_json_format_partitions fails on Debian armel and armhf builders with mismatches - Jira

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Critical
Resolution: Fixed
Affects Version/s: 10.11.1
Fix Version/s: 11.1.1, 10.11.3, 11.0.2
Component/s: Optimizer
Labels:
None

Description

Failing test(s): main.rowid_filter_innodb main.analyze_stmt_orderby main.explain_json_format_partitions main.cte_recursive main.derived_cond_pushdown main.order_by main.rowid_filter main.intersect main.except main.except_all

main.except_all                          w5 [ fail ]

        Test ended at 2023-01-12 20:20:18

CURRENT_TEST: main.except_all

--- /<<PKGBUILDDIR>>/mysql-test/main/except_all.result	2022-11-14 18:10:21.000000000 +0000

+++ /<<PKGBUILDDIR>>/mysql-test/main/except_all.reject	2023-01-12 20:20:18.132443098 +0000

@@ -115,13 +115,9 @@

 ANALYZE format=json select * from ((select a,b from t1) except all (select c,d from t2)) a;

 ANALYZE

-  "query_optimization": {

-    "r_total_time_ms": "REPLACED"

-  },

   "query_block": {

     "select_id": 1,

     "r_loops": 1,

-    "r_total_time_ms": "REPLACED",

     "nested_loop": [

         "table": {

@@ -146,7 +142,6 @@

                     "query_block": {

                       "select_id": 2,

                       "r_loops": 1,

-                      "r_total_time_ms": "REPLACED",

                       "nested_loop": [

                           "table": {

@@ -169,7 +164,6 @@

                       "select_id": 3,

                       "operation": "EXCEPT",

                       "r_loops": 1,

-                      "r_total_time_ms": "REPLACED",

                       "nested_loop": [

                           "table": {

@@ -199,13 +193,9 @@

 ANALYZE format=json select * from ((select a from t1) except all (select c from t2)) a;

 ANALYZE

-  "query_optimization": {

-    "r_total_time_ms": "REPLACED"

-  },

   "query_block": {

     "select_id": 1,

     "r_loops": 1,

-    "r_total_time_ms": "REPLACED",

     "nested_loop": [

         "table": {

@@ -230,7 +220,6 @@

                     "query_block": {

                       "select_id": 2,

                       "r_loops": 1,

-                      "r_total_time_ms": "REPLACED",

                       "nested_loop": [

                           "table": {

@@ -253,7 +242,6 @@

                       "select_id": 3,

                       "operation": "EXCEPT",

                       "r_loops": 1,

-                      "r_total_time_ms": "REPLACED",

                       "nested_loop": [

                           "table": {

@@ -469,9 +457,6 @@

 ANALYZE format=json (select a,b,e,f from t1,t3) except all (select c,d,g,h from t2,t4);

 ANALYZE

-  "query_optimization": {

-    "r_total_time_ms": "REPLACED"

-  },

   "query_block": {

     "union_result": {

       "table_name": "<except1,2>",

@@ -483,7 +468,6 @@

           "query_block": {

             "select_id": 1,

             "r_loops": 1,

-            "r_total_time_ms": "REPLACED",

             "nested_loop": [

                 "table": {

@@ -525,7 +509,6 @@

             "select_id": 2,

             "operation": "EXCEPT",

             "r_loops": 1,

-            "r_total_time_ms": "REPLACED",

             "nested_loop": [

                 "table": {

@@ -569,13 +552,9 @@

 ANALYZE format=json select * from ((select a,b,e,f from t1,t3) except all (select c,d,g,h from t2,t4)) t;

 ANALYZE

-  "query_optimization": {

-    "r_total_time_ms": "REPLACED"

-  },

   "query_block": {

     "select_id": 1,

     "r_loops": 1,

-    "r_total_time_ms": "REPLACED",

     "nested_loop": [

         "table": {

@@ -600,7 +579,6 @@

                     "query_block": {

                       "select_id": 2,

                       "r_loops": 1,

-                      "r_total_time_ms": "REPLACED",

                       "nested_loop": [

                           "table": {

@@ -642,7 +620,6 @@

                       "select_id": 3,

                       "operation": "EXCEPT",

                       "r_loops": 1,

-                      "r_total_time_ms": "REPLACED",

                       "nested_loop": [

                           "table": {

mysqltest: Result length mismatch

Logs:

This is somewhat similar to ~~MDEV-11711~~ that had mismatches in JSON output on armhf only.

This is also similar to ~~MDEV-8981~~ and ~~MDEV-11866~~ where the issue was specifically the row

"r_total_time_ms": "REPLACED",

Jira MDEV-20538 is the newest in this category and only one I found still open (assigned to psergei).

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List
- Download All

my_timer_cycles-default.patch
2 kB
2023-01-20 17:11
screenshot-1.png
68 kB
2023-01-14 20:57

Issue Links

is caused by

MDEV-28926 Make ANALYZE FORMAT=JSON show time spent in the query optimizer

Closed

relates to

MDEV-33520 test main.table_value_constr fails on armhf with output missing extra 'r_total_time_ms' field

Open

MDEV-30875 main.analyze_stmt_orderby/rowid_filter_innodb/explain_json_format_partitions (+ 7 more) fails on Launchpad armhf builders

Closed

Activity

Ascending order - Click to sort in descending order

Otto Kekäläinen created issue - 2023-01-14 20:56

Otto Kekäläinen made changes - 2023-01-14 20:57

Field	Original Value	New Value
Attachment		screenshot-1.png [ 67787 ]

Otto Kekäläinen made changes - 2023-01-14 21:00

Description

On the first ever upload of MariaDB 10.11 to Debian, I noticed that various tests that compare the JSON output from the optimizer fails with mismatches on armel and armhf builds (amd64 and arm64 pass):

Failing test(s): main.rowid_filter_innodb main.analyze_stmt_orderby main.explain_json_format_partitions main.cte_recursive main.derived_cond_pushdown main.order_by main.rowid_filter main.intersect main.except main.except_all

{noformat}
main.except_all w5 [ fail ]
        Test ended at 2023-01-12 20:20:18

CURRENT_TEST: main.except_all
--- /<<PKGBUILDDIR>>/mysql-test/main/except_all.result 2022-11-14 18:10:21.000000000 +0000
+++ /<<PKGBUILDDIR>>/mysql-test/main/except_all.reject 2023-01-12 20:20:18.132443098 +0000
@@ -115,13 +115,9 @@
ANALYZE format=json select * from ((select a,b from t1) except all (select c,d from t2)) a;
ANALYZE
{
- "query_optimization": {
- "r_total_time_ms": "REPLACED"
- },
   "query_block": {
     "select_id": 1,
     "r_loops": 1,
- "r_total_time_ms": "REPLACED",
     "nested_loop": [
       {
         "table": {
@@ -146,7 +142,6 @@
                     "query_block": {
                       "select_id": 2,
                       "r_loops": 1,
- "r_total_time_ms": "REPLACED",
                       "nested_loop": [
                         {
                           "table": {
@@ -169,7 +164,6 @@
                       "select_id": 3,
                       "operation": "EXCEPT",
                       "r_loops": 1,
- "r_total_time_ms": "REPLACED",
                       "nested_loop": [
                         {
                           "table": {
@@ -199,13 +193,9 @@
ANALYZE format=json select * from ((select a from t1) except all (select c from t2)) a;
ANALYZE
{
- "query_optimization": {
- "r_total_time_ms": "REPLACED"
- },
   "query_block": {
     "select_id": 1,
     "r_loops": 1,
- "r_total_time_ms": "REPLACED",
     "nested_loop": [
       {
         "table": {
@@ -230,7 +220,6 @@
                     "query_block": {
                       "select_id": 2,
                       "r_loops": 1,
- "r_total_time_ms": "REPLACED",
                       "nested_loop": [
                         {
                           "table": {
@@ -253,7 +242,6 @@
                       "select_id": 3,
                       "operation": "EXCEPT",
                       "r_loops": 1,
- "r_total_time_ms": "REPLACED",
                       "nested_loop": [
                         {
                           "table": {
@@ -469,9 +457,6 @@
ANALYZE format=json (select a,b,e,f from t1,t3) except all (select c,d,g,h from t2,t4);
ANALYZE
{
- "query_optimization": {
- "r_total_time_ms": "REPLACED"
- },
   "query_block": {
     "union_result": {
       "table_name": "<except1,2>",
@@ -483,7 +468,6 @@
           "query_block": {
             "select_id": 1,
             "r_loops": 1,
- "r_total_time_ms": "REPLACED",
             "nested_loop": [
               {
                 "table": {
@@ -525,7 +509,6 @@
             "select_id": 2,
             "operation": "EXCEPT",
             "r_loops": 1,
- "r_total_time_ms": "REPLACED",
             "nested_loop": [
               {
                 "table": {
@@ -569,13 +552,9 @@
ANALYZE format=json select * from ((select a,b,e,f from t1,t3) except all (select c,d,g,h from t2,t4)) t;
ANALYZE
{
- "query_optimization": {
- "r_total_time_ms": "REPLACED"
- },
   "query_block": {
     "select_id": 1,
     "r_loops": 1,
- "r_total_time_ms": "REPLACED",
     "nested_loop": [
       {
         "table": {
@@ -600,7 +579,6 @@
                     "query_block": {
                       "select_id": 2,
                       "r_loops": 1,
- "r_total_time_ms": "REPLACED",
                       "nested_loop": [
                         {
                           "table": {
@@ -642,7 +620,6 @@
                       "select_id": 3,
                       "operation": "EXCEPT",
                       "r_loops": 1,
- "r_total_time_ms": "REPLACED",
                       "nested_loop": [
                         {
                           "table": {

mysqltest: Result length mismatch
{noformat}

On the first ever upload of MariaDB 10.11 to Debian, I noticed that various tests that compare the JSON output from the optimizer fails with mismatches on armel and armhf builds (amd64 and arm64 pass):

!screenshot-1.png|thumbnail!

Failing test(s): main.rowid_filter_innodb main.analyze_stmt_orderby main.explain_json_format_partitions main.cte_recursive main.derived_cond_pushdown main.order_by main.rowid_filter main.intersect main.except main.except_all

{noformat}
main.except_all w5 [ fail ]
        Test ended at 2023-01-12 20:20:18

CURRENT_TEST: main.except_all
--- /<<PKGBUILDDIR>>/mysql-test/main/except_all.result 2022-11-14 18:10:21.000000000 +0000
+++ /<<PKGBUILDDIR>>/mysql-test/main/except_all.reject 2023-01-12 20:20:18.132443098 +0000
@@ -115,13 +115,9 @@
ANALYZE format=json select * from ((select a,b from t1) except all (select c,d from t2)) a;
ANALYZE
{
- "query_optimization": {
- "r_total_time_ms": "REPLACED"
- },
   "query_block": {
     "select_id": 1,
     "r_loops": 1,
- "r_total_time_ms": "REPLACED",
     "nested_loop": [
       {
         "table": {
@@ -146,7 +142,6 @@
                     "query_block": {
                       "select_id": 2,
                       "r_loops": 1,
- "r_total_time_ms": "REPLACED",
                       "nested_loop": [
                         {
                           "table": {
@@ -169,7 +164,6 @@
                       "select_id": 3,
                       "operation": "EXCEPT",
                       "r_loops": 1,
- "r_total_time_ms": "REPLACED",
                       "nested_loop": [
                         {
                           "table": {
@@ -199,13 +193,9 @@
ANALYZE format=json select * from ((select a from t1) except all (select c from t2)) a;
ANALYZE
{
- "query_optimization": {
- "r_total_time_ms": "REPLACED"
- },
   "query_block": {
     "select_id": 1,
     "r_loops": 1,
- "r_total_time_ms": "REPLACED",
     "nested_loop": [
       {
         "table": {
@@ -230,7 +220,6 @@
                     "query_block": {
                       "select_id": 2,
                       "r_loops": 1,
- "r_total_time_ms": "REPLACED",
                       "nested_loop": [
                         {
                           "table": {
@@ -253,7 +242,6 @@
                       "select_id": 3,
                       "operation": "EXCEPT",
                       "r_loops": 1,
- "r_total_time_ms": "REPLACED",
                       "nested_loop": [
                         {
                           "table": {
@@ -469,9 +457,6 @@
ANALYZE format=json (select a,b,e,f from t1,t3) except all (select c,d,g,h from t2,t4);
ANALYZE
{
- "query_optimization": {
- "r_total_time_ms": "REPLACED"
- },
   "query_block": {
     "union_result": {
       "table_name": "<except1,2>",
@@ -483,7 +468,6 @@
           "query_block": {
             "select_id": 1,
             "r_loops": 1,
- "r_total_time_ms": "REPLACED",
             "nested_loop": [
               {
                 "table": {
@@ -525,7 +509,6 @@
             "select_id": 2,
             "operation": "EXCEPT",
             "r_loops": 1,
- "r_total_time_ms": "REPLACED",
             "nested_loop": [
               {
                 "table": {
@@ -569,13 +552,9 @@
ANALYZE format=json select * from ((select a,b,e,f from t1,t3) except all (select c,d,g,h from t2,t4)) t;
ANALYZE
{
- "query_optimization": {
- "r_total_time_ms": "REPLACED"
- },
   "query_block": {
     "select_id": 1,
     "r_loops": 1,
- "r_total_time_ms": "REPLACED",
     "nested_loop": [
       {
         "table": {
@@ -600,7 +579,6 @@
                     "query_block": {
                       "select_id": 2,
                       "r_loops": 1,
- "r_total_time_ms": "REPLACED",
                       "nested_loop": [
                         {
                           "table": {
@@ -642,7 +620,6 @@
                       "select_id": 3,
                       "operation": "EXCEPT",
                       "r_loops": 1,
- "r_total_time_ms": "REPLACED",
                       "nested_loop": [
                         {
                           "table": {

mysqltest: Result length mismatch
{noformat}

Logs:
* https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=armel&ver=1%3A10.11.1-1%7Eexp1&stamp=1673554836&raw=0
* https://buildd.debian.org/status/fetch.php?pkg=mariadb&arch=armhf&ver=1%3A10.11.1-1%7Eexp1&stamp=1673555764&raw=0

This is somewhat similar to ~~MDEV-11711~~ that had mismatches in JSON output on armhf only.

This is also similar to ~~MDEV-8981~~ and ~~MDEV-11866~~ where the issue was specifically the row

{noformat}
"r_total_time_ms": "REPLACED",
{noformat}

Jira MDEV-20538 is the newest in this category and only one I found still open (assigned to [~psergei]).

Daniel Black added a comment - 2023-01-14 22:15

Debian non-supported-upstream arches already notified of this and shown where to do a 1-2 line change.

Request ref.

noting armel, armhf, hppa, sparc64 unsupported upstream:

If a (include/my_rdtsc.h) static inline ulonglong my_timer_cycles(void) implementation for those is provided, all the "ANALYZE format=json" tests, will pass.

Contributions welcome ( https://github.com/MariaDB/server/tree/10.11/include/my_rdtsc.h) (10.4+)

I guess we'll see if they are going to support their architectures.

If MTR supported json expression output, mysql-test/include/analyze-format.inc could remove r_total_time_ms.

Daniel Black added a comment - 2023-01-14 22:15 Debian non-supported-upstream arches already notified of this and shown where to do a 1-2 line change. Request ref . noting armel, armhf, hppa, sparc64 unsupported upstream: If a (include/my_rdtsc.h) static inline ulonglong my_timer_cycles(void) implementation for those is provided, all the "ANALYZE format=json" tests, will pass. Contributions welcome ( https://github.com/MariaDB/server/tree/10.11/include/my_rdtsc.h ) (10.4+) I guess we'll see if they are going to support their architectures. If MTR supported json expression output, mysql-test/include/analyze-format.inc could remove r_total_time_ms.

Otto Kekäläinen added a comment - 2023-01-15 23:19

The same is visible also on https://launchpadlibrarian.net/644154363/buildlog_ubuntu-lunar-armhf.mariadb_1%3A10.11.1-1~exp1~ubuntu23.04.1~1672817558.953d5feaf75.debian.experimental_BUILDING.txt.gz - seems all tests with JSON EXPLAIN output has this and they fail. Thus it can't be worked around by simply skipping a couple of tests.

Otto Kekäläinen added a comment - 2023-01-15 23:19 The same is visible also on https://launchpadlibrarian.net/644154363/buildlog_ubuntu-lunar-armhf.mariadb_1%3A10.11.1-1~exp1~ubuntu23.04.1~1672817558.953d5feaf75.debian.experimental_BUILDING.txt.gz - seems all tests with JSON EXPLAIN output has this and they fail. Thus it can't be worked around by simply skipping a couple of tests.

Adrian Bunk made changes - 2023-01-20 17:11

Attachment

my_timer_cycles-default.patch [ 67891 ]

Adrian Bunk added a comment - 2023-01-20 17:13

I've just attached my_timer_cycles-default.patch, which uses my_timer_microseconds() as fallback implementation for my_timer_cycles().

This is the fastest (effectively one-line change) hack for getting this test failure fixed, but likely not a good fix.

Adrian Bunk added a comment - 2023-01-20 17:13 I've just attached my_timer_cycles-default.patch, which uses my_timer_microseconds() as fallback implementation for my_timer_cycles(). This is the fastest (effectively one-line change) hack for getting this test failure fixed, but likely not a good fix.

Otto Kekäläinen added a comment - 2023-01-21 05:00

This is tracked in Debian as: https://bugs.debian.org/1029163

I think this is quite a relevant thing to fix as it affects the architecture used in Raspberry PIs, and they are quite popular.

Eric_Herman Are you familiar with the topic https://github.com/MariaDB/server/tree/10.11/include/my_rdtsc.h?
Do you want to review the patch attached here (and same patch pending at https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/28)?

Otto Kekäläinen added a comment - 2023-01-21 05:00 This is tracked in Debian as: https://bugs.debian.org/1029163 I think this is quite a relevant thing to fix as it affects the architecture used in Raspberry PIs, and they are quite popular. Eric_Herman Are you familiar with the topic https://github.com/MariaDB/server/tree/10.11/include/my_rdtsc.h? Do you want to review the patch attached here (and same patch pending at https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/28)?

Daniel Black added a comment - 2023-01-21 23:32

AdrianBunk thanks for your patch an comments.

From your comments you suggest std::chrono::high_resolution_clock may be an option. I'm open to moving the few c files that use this to C++ (especially as its C++11).

list of c files using my_rdtsc.h

mysys/my_cpu.c
mysys/my_delete.c
mysys/my_rdtsc.c
sql/sql_analyze_stmt.h
storage/perfschema/pfs_timer.cc
unittest/mysys/my_rdtsc-t.c

Can you please:

use std::chrono::high_resolution_clock in include/my_rdtsc.h
rename unittest/mysys/my_rdtsc-t.c -> unittest/mysys/my_rdtsc-t.cc (as a first test and its entry in CMakeList.txt)
optional: my_timer_init_frequency might be better initialized from std::chrono::high_resolution_clock.period (though if a comparison with the existing self measurement is possible that would be insightful)
build and run unit test cmake --build . --target my_rdtsc-t && unittest/mysys/my_rdtsc-t, (include output here)

I can handle the renaming of other files.

Daniel Black added a comment - 2023-01-21 23:32 AdrianBunk thanks for your patch an comments. From your comments you suggest std::chrono::high_resolution_clock may be an option. I'm open to moving the few c files that use this to C++ (especially as its C++11). list of c files using my_rdtsc.h mysys/my_cpu.c mysys/my_delete.c mysys/my_rdtsc.c sql/sql_analyze_stmt.h storage/perfschema/pfs_timer.cc unittest/mysys/my_rdtsc-t.c Can you please: use std::chrono::high_resolution_clock in include/my_rdtsc.h rename unittest/mysys/my_rdtsc-t.c -> unittest/mysys/my_rdtsc-t.cc (as a first test and its entry in CMakeList.txt) optional: my_timer_init_frequency might be better initialized from std::chrono::high_resolution_clock.period (though if a comparison with the existing self measurement is possible that would be insightful) build and run unit test cmake --build . --target my_rdtsc-t && unittest/mysys/my_rdtsc-t , (include output here) I can handle the renaming of other files.

Eric Herman added a comment - 2023-01-22 02:33

I am not yet familiar with the topic, yet it seems like it might be "up my street", thus I shall take a look in the coming days.

Eric Herman added a comment - 2023-01-22 02:33 I am not yet familiar with the topic, yet it seems like it might be "up my street", thus I shall take a look in the coming days.

Adrian Bunk added a comment - 2023-01-22 07:37 - edited

@danblack Your first test does not work due to MY_ADD_TESTS having SET(ARG_EXT "c"). That's likely easier to test by someone who understands your build system better.

Using std::chrono::high_resolution_clock is not my suggestion, it's from the TODO in the comment above my_timer_cycles() in include/my_rdtsc.h. Based on the Notes at https://en.cppreference.com/w/cpp/chrono/high_resolution_clock std::chrono::steady_clock might be a better option.

Adrian Bunk added a comment - 2023-01-22 07:37 - edited @danblack Your first test does not work due to MY_ADD_TESTS having SET(ARG_EXT "c") . That's likely easier to test by someone who understands your build system better. Using std::chrono::high_resolution_clock is not my suggestion, it's from the TODO in the comment above my_timer_cycles() in include/my_rdtsc.h . Based on the Notes at https://en.cppreference.com/w/cpp/chrono/high_resolution_clock std::chrono::steady_clock might be a better option.

Daniel Black added a comment - 2023-01-23 07:06

I had a look at the C++ and while resturning std::chrono::time_point was easy I didn't want to restructure it enough to go back to getting intervals and returning difference.

I found that clock_gettime is a vdso function linux on all architectures (except hppa) and this is what's used by my_interval_timer.

lizardo, is this acceptable? https://github.com/MariaDB/server/pull/2448

AdrianBunk, If not acceptable, could my_timer_cycles would return my_timer_nanoseconds (rather than milliseconds) be acceptable?

Daniel Black added a comment - 2023-01-23 07:06 I had a look at the C++ and while resturning std::chrono::time_point was easy I didn't want to restructure it enough to go back to getting intervals and returning difference. I found that clock_gettime is a vdso function linux on all architectures (except hppa) and this is what's used by my_interval_timer. lizardo , is this acceptable? https://github.com/MariaDB/server/pull/2448 AdrianBunk , If not acceptable, could my_timer_cycles would return my_timer_nanoseconds (rather than milliseconds) be acceptable?

Daniel Black made changes - 2023-01-23 07:06

Fix Version/s

10.11 [ 27614 ]

Daniel Black made changes - 2023-01-23 07:06

Link

This issue is caused by ~~MDEV-28926~~ [ ~~MDEV-28926~~ ]

Daniel Black made changes - 2023-01-23 07:07

Assignee

Daniel Black [ danblack ]

Daniel Black made changes - 2023-01-23 07:07

Status

Open [ 1 ]

Confirmed [ 10101 ]

Daniel Black made changes - 2023-01-23 07:07

Assignee	Daniel Black [ danblack ]	Luis Eduardo Oliveira Lizardo [ JIRAUSER51996 ]
Status	Confirmed [ 10101 ]	In Review [ 10002 ]

Daniel Black made changes - 2023-01-23 07:07

Priority

Major [ 3 ]

Critical [ 2 ]

Daniel Black made changes - 2023-01-30 21:05

Assignee

Luis Eduardo Oliveira Lizardo [ JIRAUSER51996 ]

Michael Widenius [ monty ]

Daniel Black made changes - 2023-02-07 00:35

Assignee

Michael Widenius [ monty ]

Sergei Petrunia [ psergey ]

Otto Kekäläinen added a comment - 2023-03-19 06:10

For the record, I have not encountered this failure on Launchpad or Debian builders since https://github.com/MariaDB/server/pull/2448 was backported to Debian in https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/340b190ac8a38dc60e176b136966229d40d14b2b

Otto Kekäläinen added a comment - 2023-03-19 06:10 For the record, I have not encountered this failure on Launchpad or Debian builders since https://github.com/MariaDB/server/pull/2448 was backported to Debian in https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/340b190ac8a38dc60e176b136966229d40d14b2b

Sergei Petrunia added a comment - 2023-04-24 14:42

Review comments in the PR. Ok to push after addressed.

Sergei Petrunia added a comment - 2023-04-24 14:42 Review comments in the PR. Ok to push after addressed.

Sergei Petrunia made changes - 2023-04-24 14:42

Assignee	Sergei Petrunia [ psergey ]	Daniel Black [ danblack ]
Status	In Review [ 10002 ]	Stalled [ 10000 ]

Daniel Black added a comment - 2023-04-27 04:43

Thanks psergei.

Daniel Black added a comment - 2023-04-27 04:43 Thanks psergei .

Daniel Black made changes - 2023-04-27 04:43

issue.field.resolutiondate

2023-04-27 04:43:14.0

2023-04-27 04:43:14.245

Daniel Black made changes - 2023-04-27 04:43

Component/s		Optimizer [ 10200 ]
Fix Version/s		10.11.3 [ 28524 ]
Fix Version/s		11.1.1 [ 28704 ]
Fix Version/s		11.0.2 [ 28706 ]
Fix Version/s	10.11 [ 27614 ]
Resolution		Fixed [ 1 ]
Status	Stalled [ 10000 ]	Closed [ 6 ]

Otto Kekäläinen made changes - 2023-10-09 05:12

Link

This issue relates to ~~MDEV-30875~~ [ ~~MDEV-30875~~ ]

Otto Kekäläinen made changes - 2024-02-22 06:15

Link

This issue relates to MDEV-33520 [ MDEV-33520 ]

People

Assignee:: Daniel Black

Reporter:: Otto Kekäläinen

Votes:: 0 Vote for this issue

Watchers:: 6 Start watching this issue

Dates

Created:: 2023-01-14 20:56

Updated:: 2024-02-22 06:15

Resolved:: 2023-04-27 04:43

Git Integration

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

MariaDB Server

Details

Description

Attachments

Attachments

Issue Links

Activity

People

Dates

Git Integration