[MDEV-29347] MariaDB 10.6.8 fails to start when ONLY_FULL_GROUP_BY gets provided Created: 2022-08-22  Updated: 2022-10-17  Resolved: 2022-09-26

Status: Closed
Project: MariaDB Server
Component/s: Time zones
Affects Version/s: 10.6.8, 10.6, 10.7, 10.8, 10.9, 10.10
Fix Version/s: 10.6.11, 10.7.7, 10.8.6, 10.9.4, 10.10.2

Type: Bug Priority: Blocker
Reporter: Simon Assignee: Sergei Golubchik
Resolution: Fixed Votes: 0
Labels: regression
Environment:

Docker container


 Description   

When starting the mariadb 10.6.8 docker container with

--sql-mode=ONLY_FULL_GROUP_BY

, it fails to initialize with

ERROR 1140 (42000) at line 2: Mixing of GROUP columns (MIN(),MAX(),COUNT(),...) with no GROUP columns is illegal if there is no GROUP BY clause

Here a more complete docker run command that we use in Nextcloud server for testing:

docker run -it --rm \
--name mariadb \
-e MYSQL_ROOT_PASSWORD=owncloud \
-e MYSQL_USER=oc_autotest \
-e MYSQL_PASSWORD=owncloud \
-e MYSQL_DATABASE=oc_autotest \
ghcr.io/nextcloud/continuous-integration-mariadb-10.6:latest \
--sql-mode=ONLY_FULL_GROUP_BY,STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_ENGINE_SUBSTITUTION

(The docker image is based on the official mariadb10.6.8 docker image and nothing is modified)

 Comments   
Comment by Elena Stepanova [ 2022-08-22 ]

Thanks for the report.

The problem is not limited to docker containers, general timezone initialization fails the same way. Apparently the failure was brought by

commit 13e77930e615f05cc74d408110e887b00e1abcc9
 
Author: Daniel Black
 
Date:   Wed Apr 6 13:12:21 2022 +1000
 
 
 
    MDEV-28263: mariadb-tzinfo-to-sql improve wsrep and binlog cases

which introduced the query in question.

Comment by Daniel Black [ 2022-08-23 ]

Thanks szaimen for the bug report.

I added a workaround that will be included in the current q3-2022 set of release soon.

Non-container users can use the same workaround. Being a blocker bug this will be corrected in the next server release.

Comment by Oleksandr Byelkin [ 2022-09-05 ]

OK to push

Comment by Simon [ 2022-09-19 ]

Hello, is there any update here? Is this already fixed in a new release?

Comment by Sergei Golubchik [ 2022-09-22 ]

No, the issue isn't closed yet. The new release was an out-of-schedule release to fix critical data corruption regressions. This fix didn't make it there, it'll be in the next scheduled release.

Generated at Thu Feb 08 10:07:50 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.