Issue Task Resolved

#110240Extend runTests.sh database version matrix

Stefan Bürk 07/20/26, 17:45 updated 07/21/26, 08:10

Description

Build/Scripts/runTests.sh restricts the selectable database versions through
the -i option. The accepted values have fallen behind the versions actually
released and used in the wild, so several current releases cannot be tested
locally at all.

Current state:

  -d mariadb    10.4 ... 11.3, 11.4          (runTests.sh:84)
  -d postgres   10 ... 16                    (runTests.sh:115)

Anything newer is rejected with “Invalid combination -d … -i …”, so a
developer cannot reproduce or investigate an issue on those versions without
editing the script first.

This affects real, supported releases:

  MariaDB 11.8   long-term release
  MariaDB 11.7   short-term / rolling
  MariaDB 11.6   short-term
  MariaDB 11.5   short-term
  PostgreSQL 18  current major
  PostgreSQL 17  current major

The gap is not academic. Issue #110234 was a genuine schema analyzer defect on
MariaDB 11.4 and newer, and confirming its behaviour on 11.7 and 11.8 required
patching the version regex by hand before the versions could even be selected.

Scope

This issue covers the runTests.sh execution matrix only:

  1. extend the MariaDB -i regex by 11.5, 11.6, 11.7 and 11.8
  2. extend the PostgreSQL -i regex by 17 and 18
  3. extend the corresponding -d mariadb and -d postgres version lists in the
    help output, including the support status of each added version
  4. confirm the container images resolve, in particular the -alpine tag variant
    used for PostgreSQL

Adjusting the GitLab CI matrix under Build/gitlab-ci is deliberately not part
of this issue. Making the versions selectable comes first; adding jobs is done
together with or after a working state has been ensured, so that CI is not
turned red by versions which are known to need further fixes.

Expected outcome

MariaDB 11.5 and 11.6 and PostgreSQL 17 and 18 are expected to behave like
their predecessors.

MariaDB 11.7 and 11.8 are expected to show failures once selectable, because
the platform elevation in the core does not recognise them and falls through to
MariaDB110700Platform. That is a separate defect and gets its own issue; it must
not block this change. Making the versions reachable is the prerequisite for
working on it.

Reviews 8