[debian-mysql] Bug#932856: mariadb-client-10.3: mysqldump uses 10.3 options with pre-10.3 servers and breaks

[Daniel Fussell]

Package: mariadb-client-10.3
Version: 1:10.3.15-1
Severity: critical
Tags: upstream
Justification: causes serious data loss

Dear Maintainer,

mysqldump is unable to backup triggers and routines from any pre-10.3
version server

From the upstream bug-report ( https://jira.mariadb.org/browse/MDEV-17429):

    When issuing a 10.3 mysqldump command to dump triggers and routines
    from a 10.2 server, the tool breaks because it tries to issue a SHOW
    PACKAGES command which is not supported in 10.2 and earlier releases.

    mysqldump --quick --routines --triggers --no-create-info
    --skip-lock-tables --no-data --compress -h 10.10.16.138 -u
    mariadb_mock_import -p myschema

    ....

    mysqldump: Couldn't execute 'SHOW PACKAGE STATUS WHERE Db =
    'myschema'': You have an error in your SQL syntax; check the manual
    that corresponds to your MariaDB server version for the right syntax
    to use near 'PACKAGE STATUS WHERE Db = 'myschema'' at line 1 (1064)

Running mysqldump without the --triggers and --routines flags will
backup the database structure and data, but will lose the associated
triggers and routines.  For admins and developers, loading the dump back
into a server would require manually creating the triggers from some
previous backup or repository (assuming a viable backup exists).

Running mysqldump with --triggers and --routines flags enabled will fail
entirely, potentially breaking backup scripts and cron jobs that depend
on it.  While this will not lose data directly, it does preclude the
option of restoring databases when a server upgrade fails, or tables are
corrupted, or when a mistaken drop/update/replace/insert statement is
issued.

A successful database dump (including triggers and routines) is expected.

The mysqldump 10.3 server version incompatibility is reported to be
fixed in 10.3.17.

-- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1), LANGUAGE=en_US
(charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mariadb-client-10.3 depends on:
ii  debianutils               4.8.6.1
ii  libc6                     2.28-10
ii  libconfig-inifiles-perl   3.000001-1
ii  libgnutls30               3.6.7-4
ii  libstdc++6                8.3.0-6
ii  mariadb-client-core-10.3  1:10.3.15-1
ii  perl                      5.28.1-6
ii  zlib1g                    1:1.2.11.dfsg-1

Versions of packages mariadb-client-10.3 recommends:
ii  libdbd-mysql-perl     4.050-2
ii  libdbi-perl           1.642-1+b1
ii  libterm-readkey-perl  2.38-1

mariadb-client-10.3 suggests no packages.

-- no debconf information
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-mysql-maint/attachments/20190723/f753a81b/attachment.html>