{"id":21770,"date":"2026-10-01T14:55:00","date_gmt":"2026-10-01T12:55:00","guid":{"rendered":"https:\/\/webhosting.de\/?p=21770"},"modified":"2026-09-30T22:06:16","modified_gmt":"2026-09-30T20:06:16","slug":"mariadb-12-features-update-and-hosting-strategy","status":"publish","type":"post","link":"https:\/\/webhosting.de\/en\/mariadb-12-features-update-hosting-strategie\/","title":{"rendered":"MariaDB 12.0: Features, Update Risks, and Hosting Strategy"},"content":{"rendered":"<div class=\"wh-article\" data-wh-layout=\"2.1.2\" style=\"width:100%;max-width:820px;margin:0 auto;color:#263b4b;font-family:inherit;font-size:18px;line-height:1.8;text-align:start;overflow-wrap:break-word;box-sizing:border-box\"><p class=\"wh-lead\" style=\"font-size:20px;line-height:1.7;color:#233746;margin:0 0 1.1em\">MariaDB 12.0 enhances the database server in areas such as query planning, auditing, replication, and encryption. For hosting platforms, however, it is not the version number that matters, but rather the <strong style=\"font-weight:700;color:inherit\">specifically verified target value<\/strong>: MariaDB 12.0.2 is documented as a stable GA release, while the series follows the rolling release model. Before updating MariaDB, the package status, applications, configuration, recovery, and operational model must all be evaluated together.    <\/p>\n<nav class=\"wh-toc\" aria-label=\"Contents of this article\" style=\"display:block;margin:28px 0 38px;padding:22px;border:1px solid #d9e4e8;border-radius:14px;background:#f4f8f8\"><p class=\"wh-toc-title\" style=\"font-size:13px;font-weight:700;letter-spacing:.08em;color:#49656b;margin:0 0 14px\">Go directly to the section<\/p><div class=\"wh-toc-grid\" style=\"display:grid;grid-template-columns:repeat(auto-fit,minmax(min(100%,280px),1fr));gap:10px\"><div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#version-und-release-modell\" style=\"display:block;height:100%;padding:12px 15px;border:1px solid #dce6e8;border-radius:9px;background:#fff;color:#18575b;font-size:14px;line-height:1.5;font-weight:600;text-decoration:none;box-sizing:border-box\">Classifying MariaDB 12.0 Correctly<\/a><\/div>\n<div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#rolling-release-oder-lts\" style=\"display:block;height:100%;padding:12px 15px;border:1px solid #dce6e8;border-radius:9px;background:#fff;color:#18575b;font-size:14px;line-height:1.5;font-weight:600;text-decoration:none;box-sizing:border-box\">Distinguishing Between Rolling Release and LTS<\/a><\/div>\n<div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#funktionen-und-kompatibilitaet\" style=\"display:block;height:100%;padding:12px 15px;border:1px solid #dce6e8;border-radius:9px;background:#fff;color:#18575b;font-size:14px;line-height:1.5;font-weight:600;text-decoration:none;box-sizing:border-box\">Evaluating New Features with Limitations<\/a><\/div>\n<div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#releasestatus-und-einsatzfaelle\" style=\"display:block;height:100%;padding:12px 15px;border:1px solid #dce6e8;border-radius:9px;background:#fff;color:#18575b;font-size:14px;line-height:1.5;font-weight:600;text-decoration:none;box-sizing:border-box\">Compare Release Status and Features<\/a><\/div>\n<div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#update-pfad-und-pruefungen\" style=\"display:block;height:100%;padding:12px 15px;border:1px solid #dce6e8;border-radius:9px;background:#fff;color:#18575b;font-size:14px;line-height:1.5;font-weight:600;text-decoration:none;box-sizing:border-box\">Carefully Prepare for a MariaDB Update<\/a><\/div>\n<div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#abfragen-proxys-und-replikation\" style=\"display:block;height:100%;padding:12px 15px;border:1px solid #dce6e8;border-radius:9px;background:#fff;color:#18575b;font-size:14px;line-height:1.5;font-weight:600;text-decoration:none;box-sizing:border-box\">Configure Special Cases Safely<\/a><\/div>\n<div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#identitaetswechsel-und-audit\" style=\"display:block;height:100%;padding:12px 15px;border:1px solid #dce6e8;border-radius:9px;background:#fff;color:#18575b;font-size:14px;line-height:1.5;font-weight:600;text-decoration:none;box-sizing:border-box\">Ensuring Session Transition and Audit Security<\/a><\/div>\n<div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#betrieb-und-fehlersuche\" style=\"display:block;height:100%;padding:12px 15px;border:1px solid #dce6e8;border-radius:9px;background:#fff;color:#18575b;font-size:14px;line-height:1.5;font-weight:600;text-decoration:none;box-sizing:border-box\">Monitor Operation After the Upgrade<\/a><\/div>\n<div class=\"wh-toc-item\" style=\"display:block;min-width:0;margin:0;padding:0\"><a class=\"wh-toc-link\" href=\"#entscheidung-fuer-plattformen\" style=\"display:block;height:100%;padding:12px 15px;border:1px solid #dce6e8;border-radius:9px;background:#fff;color:#18575b;font-size:14px;line-height:1.5;font-weight:600;text-decoration:none;box-sizing:border-box\">Strategically Determine the Target Score<\/a><\/div>\n<\/div><\/nav><section class=\"wh-section\" aria-labelledby=\"version-und-release-modell\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"version-und-release-modell\" style=\"margin:38px 0 18px;color:#172f41;font-size:clamp(24px,1.25rem + 1vw,30px);font-weight:700;line-height:1.3;scroll-margin-top:115px\">Classifying MariaDB 12.0 Correctly<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The term \u201eMariaDB 12\u201c does not refer to a single, permanently maintained product release. For specific technical information, see the rolling series <strong style=\"font-weight:700;color:inherit\">MariaDB 12.0<\/strong> That is what is meant. Within this series, the releases represent different levels of maturity: 12.0.0 was released on March 26, 2025, as a preview, 12.0.1 on June 5, 2025, as a release candidate, and 12.0.2 on August 7, 2025, as a stable GA release.   <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Preview and Release Candidate versions are intended for testing and should not be equated with a stable platform release. The fact that 12.0.2 is documented as Stable or GA, on the other hand, accurately describes the maturity status of this specific release. It does not follow from this that every installation should be upgraded immediately, nor that subsequent releases will automatically have the same features, packages, or operational limits. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Later branches such as 12.1, 12.2, or 12.3 must also be considered separately. Features, bug fixes, or changed default values from such series do not constitute evidence of <strong style=\"font-weight:700;color:inherit\">MariaDB 12<\/strong>.0. The same applies to development branches: An announcement or documentation there does not replace a statement regarding the published community server version.<\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Before a rollout, the platform therefore needs to be reconciled again with the package status that is actually planned. In particular, the following must be checked: the available server series, compatible client and add-on packages, support provided by the operating system version in use, and the current release classification. Repository contents and distribution packages may differ from the general product designation.<\/p>\n<aside class=\"wh-callout\" style=\"display:block;margin:28px 0;padding:20px 23px;border:1px solid #d1e4dd;border-left:4px solid #187065;border-radius:11px;background:#f0f7f4\"><p class=\"wh-callout-title\" style=\"margin:0 0 8px;color:#1c5c53;font-size:16px;font-weight:700;line-height:1.5\">Check the version status before the rollout<\/p><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">A documented GA status is an important prerequisite, but it does not constitute a release decision. The decisive factors are the specific package status that can be installed, the tested environment, and the support commitments applicable to the platform.<\/p>\n<\/aside><\/section><section class=\"wh-section\" aria-labelledby=\"rolling-release-oder-lts\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"rolling-release-oder-lts\" style=\"margin:38px 0 18px;color:#172f41;font-size:clamp(24px,1.25rem + 1vw,30px);font-weight:700;line-height:1.3;scroll-margin-top:115px\">Distinguishing Between Rolling Release and LTS<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">For hosting platforms, it is not only the version number that matters, but also the underlying <strong style=\"font-weight:700;color:inherit\">Release Model<\/strong>. MariaDB distinguishes between Innovation Releases and LTS Releases. Innovation Releases introduce new features at short intervals and, once they reach general availability (GA), typically transition to the next rolling series. LTS Releases, on the other hand, are supported for three years after GA, according to the vendor.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">A stable GA release therefore only answers the question of whether this specific version has been released as stable. It does not provide a general answer as to how long security fixes will be available, whether a distributor will continue to provide packages, or whether an existing customer base can remain on the series without migrating. These points depend on the contract, the distribution, and the current release overview. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">An innovation series may be appropriate if a platform wants to implement a clearly needed feature early on and can test the affected applications, connectors, and operational processes in isolation. To do this, teams must plan to continue along the intended upgrade path in a timely manner. This increases the effort required for approvals, communication, and fallback procedures, particularly for multi-tenant offerings.<\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">A <strong style=\"font-weight:700;color:inherit\">LTS Target Score<\/strong> It is better suited to standardized platforms with many traditional applications, where predictable maintenance windows and long-term software stability are more important than individual new features. This is not a rule against innovation releases: The key factor is whether the benefits of a feature justify the additional testing and the expected transition to the next version.<\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The selection should therefore take into account, at a minimum, functional requirements, the current package and support status, tested application compatibility, recoverability, and personnel-related operational costs. For a new installation, it is not enough to simply consider \u201eMariaDB 12\u201c the most up-to-date version. The platform deliberately balances short-term feature utilization with a long-term, standardized database configuration.<\/p>\n<aside class=\"wh-callout wh-callout-warning\" style=\"display:block;margin:28px 0;padding:20px 23px;border:1px solid #d1e4dd;border-left:4px solid #187065;border-radius:11px;background:#f0f7f4\"><p class=\"wh-callout-title\" style=\"margin:0 0 8px;color:#1c5c53;font-size:16px;font-weight:700;line-height:1.5\">Do not confuse GA with long-term care<\/p><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">No general conclusions regarding future security provision or suitability as a platform standard can be drawn from the GA status of a rolling series.<\/p>\n<\/aside><\/section><section class=\"wh-section\" aria-labelledby=\"funktionen-und-kompatibilitaet\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"funktionen-und-kompatibilitaet\" style=\"margin:38px 0 18px;color:#172f41;font-size:clamp(24px,1.25rem + 1vw,30px);font-weight:700;line-height:1.3;scroll-margin-top:115px\">Evaluating New Features with Limitations<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">MariaDB 12.0 Adds <strong style=\"font-weight:700;color:inherit\">Optimizer Hints<\/strong> to more specifically influence execution plans, such as for join orders, range optimization, or specific join algorithms. Extensions also apply to descending-order index components in loose index scans and index condition pushdown. For hosting environments, this is primarily a diagnostic tool for individual problematic queries; it is not a substitute for appropriate indexes, correct join conditions, and up-to-date table statistics.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">A hint can limit an undesirable plan, but it may itself have a negative effect as data grows or statistics change. It therefore belongs in a reproducible analysis of the affected application and not as a global setting in the <strong style=\"font-weight:700;color:inherit\">database server<\/strong>. For typical CMS and e-commerce databases, the mere availability of such hints is not a compelling reason to update to MariaDB.<\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">During an audit, the Audit Plugin in 12.0 also logs the host and port of incoming connections, as well as the TLS version used. For access behind proxies, NAT, or load balancers, this can improve forensic tracing. However, the benefit is only realized through centralized, access-protected log collection and defined retention policies; additional log data must fit within capacity and data protection planning.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">For encryption, SHA-2 support is available in <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">file_key_management.so<\/code> and <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">ssl_passphrase<\/code> Building blocks are ready. Replication environments now have options for temporary tables as well as a variable for handling events with their own server ID. In addition, version 12.0 introduces, among other things, <strong style=\"font-weight:700;color:inherit\">SYS_REFCURSOR<\/strong>, a cursor limit per session, and GIS functions such as validation, simplification, and geohash conversion. These tools are each designed to work only with specific applications and topologies.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">MariaDB Server, MaxScale, and Galera remain separate components: MaxScale has its own versions and configurations, and changes related to Galera affect only clusters. Likewise, MySQL compatibility does not imply interchangeability without verification. MariaDB uses its own GTID model and, for example, does not support MySQL's <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">SET PERSIST<\/code>. New GIS features can benefit MySQL 8-based geodata applications, but they are generally not a reason to upgrade for typical web databases.  <\/p>\n<\/section><section class=\"wh-section\" aria-labelledby=\"releasestatus-und-einsatzfaelle\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"releasestatus-und-einsatzfaelle\" style=\"margin:38px 0 18px;color:#172f41;font-size:clamp(24px,1.25rem + 1vw,30px);font-weight:700;line-height:1.3;scroll-margin-top:115px\">Compare Release Status and Features<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">For platform operation, the specific version within the series is crucial. MariaDB 12.0.0 was a preview, 12.0.1 was a release candidate, and only 12.0.2 is documented as stable or GA. These statuses indicate different levels of maturity; they do not indicate whether the series is suitable for a specific hosting rollout, operating system, or support contract.   <\/p>\n<div class=\"wh-table-scroll\" tabindex=\"0\" role=\"region\" aria-label=\"Maturity Status of the Documented MariaDB 12.0 Releases\" style=\"width:100%;max-width:100%;overflow-x:auto;margin:28px 0;border:1px solid #dce5e9;border-radius:14px;background:#fff;box-shadow:0 10px 28px -16px rgba(24,47,60,.32);box-sizing:border-box\"><table style=\"width:100%;min-width:580px;border-collapse:separate;border-spacing:0;border:0;margin:0;font-size:15px;line-height:1.6;background:#fff\"><caption style=\"padding:20px;text-align:start;font-size:17px;line-height:1.5;font-weight:700;color:#173246;background:#fff\">Maturity Status of the Documented MariaDB 12.0 Releases<\/caption><thead><tr><th scope=\"col\" style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#19394d;color:#fff\">Release<\/th><th scope=\"col\" style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#19394d;color:#fff\">Date<\/th><th scope=\"col\" style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#19394d;color:#fff\">Maturity Status<\/th><th scope=\"col\" style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#19394d;color:#fff\">Organizational Classification<\/th><\/tr><\/thead><tbody><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">12.0.0<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">March 26, 2025<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Preview<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Do not plan for this as a standard platform feature; it is intended for early functional evaluation.<\/td><\/tr><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">12.0.1<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">June 5, 2025<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Release Candidate<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">For limited compatibility testing; not intended as a basis for a broad rollout.<\/td><\/tr><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">12.0.2<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">August 7, 2025<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Stable \/ GA<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Stable, documented status of the 12.0 series; however, check the package, support, and operating system status separately.<\/td><\/tr><\/tbody><\/table><\/div><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">New features are especially useful when they address a specific operational problem. <strong style=\"font-weight:700;color:inherit\">Optimizer Hints<\/strong> can, for example, limit an undesirable execution plan for a single complex query. They are no substitute for appropriate indexes, correct join conditions, or up-to-date statistics, and should not be used as a global default for customer applications.  <\/p>\n<div class=\"wh-table-scroll\" tabindex=\"0\" role=\"region\" aria-label=\"MariaDB 12.0 Features as Targeted Tools in Hosting\" style=\"width:100%;max-width:100%;overflow-x:auto;margin:28px 0;border:1px solid #dce5e9;border-radius:14px;background:#fff;box-shadow:0 10px 28px -16px rgba(24,47,60,.32);box-sizing:border-box\"><table style=\"width:100%;min-width:580px;border-collapse:separate;border-spacing:0;border:0;margin:0;font-size:15px;line-height:1.6;background:#fff\"><caption style=\"padding:20px;text-align:start;font-size:17px;line-height:1.5;font-weight:700;color:#173246;background:#fff\">MariaDB 12.0 Features as Targeted Tools in Hosting<\/caption><thead><tr><th scope=\"col\" style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#19394d;color:#fff\">Function<\/th><th scope=\"col\" style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#19394d;color:#fff\">Potential Benefits of Hosting<\/th><th scope=\"col\" style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#19394d;color:#fff\">Prerequisite or Risk<\/th><th scope=\"col\" style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#19394d;color:#fff\">Suitable Application<\/th><\/tr><\/thead><tbody><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Optimizer Hints<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Targeted Narrowing of Problematic Individual Queries<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">The plan may have negative consequences if the data set is different<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Reproducible Reporting Error Following Analysis<\/td><\/tr><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Audit by Host, Port, and TLS Version<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Better Tracking of Accesses Behind a Proxy or NAT<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Centralized, secure log collection required<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Forensics and Transparent Platform Operations<\/td><\/tr><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">ssl_passphrase and SHA-2 for file_key_management<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Support password-protected keys<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">No substitute for rotation, a rights strategy, and a restore plan<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Defined Encryption and Key Management<\/td><\/tr><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">create_tmp_table_binlog_formats<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Managing Temporary Tables More Effectively in Replication Scenarios<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">You must understand the binlog format and topology<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Targeted Testing of Replication Architecture<\/td><\/tr><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">SYS_REFCURSOR and max_open_cursors<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Limit Stored Routines and Open Cursors<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">The application may fail if the limit is too tight<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Specialized Routine Applications<\/td><\/tr><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">GIS Features<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Expand Geodata Functions for Suitable Applications<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Often of no use for CMS and e-commerce databases<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">The application processes spatial data<\/td><\/tr><\/tbody><\/table><\/div><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The additional audit fields can capture the host, port, and TLS version used for an incoming connection. The key option <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">ssl_passphrase<\/code> On the other hand, the advanced GIS or cursor functions do not justify a blanket version upgrade. Their benefits are realized only in applications whose architecture, data model, and security requirements actually necessitate these capabilities.  <\/p>\n<\/section><section class=\"wh-section\" aria-labelledby=\"update-pfad-und-pruefungen\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"update-pfad-und-pruefungen\" style=\"margin:38px 0 18px;color:#172f41;font-size:clamp(24px,1.25rem + 1vw,30px);font-weight:700;line-height:1.3;scroll-margin-top:115px\">Carefully Prepare for a MariaDB Update<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">A MariaDB update in managed or shared hosting begins with an inventory: instances, databases, connectors, plugins, configuration files, replication paths, and affected applications must all be identified. This is followed by a staging environment that replicates production data and configuration only within the permitted security parameters. This allows startup issues and SQL discrepancies to be identified before multiple clients are affected.<\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Before any limited rollout, a complete backup and a documented recovery procedure are required. It is not enough simply to have backup files; those responsible must verify that a consistent data state usable by applications can be restored from them. They then check logins, write operations, background jobs, and typical customer paths as <strong style=\"font-weight:700;color:inherit\">Application Regression<\/strong>. The specific procedure depends on the security method used and the platform architecture.<\/p>\n<figure class=\"wp-block-image size-large wh-figure\" aria-describedby=\"wh-caption-detail1\" style=\"display:block;float:none;clear:both;width:100%;max-width:760px;margin:34px auto 40px;border:1px solid #dae5e9;border-radius:14px;overflow:hidden;background:#f5f8fa;box-shadow:0 10px 28px -17px rgba(24,47,60,.28);box-sizing:border-box\"><div class=\"wh-figure-media\" style=\"display:block;background:#eef3f5;line-height:0\"><img loading=\"lazy\" width=\"800\" height=\"534\" src=\"https:\/\/webhosting.de\/wp-content\/uploads\/2026\/09\/mariadb-update-konfiguration-backup-e0d29244-detail1-aaa5cdbba5-1024x683.webp\" class=\"wp-image-21775\" alt=\"Configuration Check and Backup Planning Before a MariaDB Update\" decoding=\"async\" srcset=\"https:\/\/webhosting.de\/wp-content\/uploads\/2026\/09\/mariadb-update-konfiguration-backup-e0d29244-detail1-aaa5cdbba5-1024x683.webp 1024w, https:\/\/webhosting.de\/wp-content\/uploads\/2026\/09\/mariadb-update-konfiguration-backup-e0d29244-detail1-aaa5cdbba5-300x200.webp 300w, https:\/\/webhosting.de\/wp-content\/uploads\/2026\/09\/mariadb-update-konfiguration-backup-e0d29244-detail1-aaa5cdbba5-768x512.webp 768w, https:\/\/webhosting.de\/wp-content\/uploads\/2026\/09\/mariadb-update-konfiguration-backup-e0d29244-detail1-aaa5cdbba5-18x12.webp 18w, https:\/\/webhosting.de\/wp-content\/uploads\/2026\/09\/mariadb-update-konfiguration-backup-e0d29244-detail1-aaa5cdbba5.webp 1536w\" sizes=\"auto, (max-width: 800px) 100vw, 800px\" ><\/div><figcaption class=\"wh-caption\" id=\"wh-caption-detail1\" style=\"display:block;margin:0;padding:12px 18px 15px;border-top:1px solid #dce5e9;color:#506575;background:#f5f8fa;font-size:14px;line-height:1.55;text-align:start\">AI-generated stock image: Configuration, recovery, and package planning must be completed before the phased rollout.<\/figcaption><\/figure><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">A fallback plan specifies who decides which data states are authoritative and how applications revert to the previous consistent state in the event of an interruption. This is standard operational practice, not a feature of a specific MariaDB version. Replication, monitoring, and failover must therefore be tested within the respective staging topology, rather than assuming they function correctly based on a successful update of a single instance.<\/p>\n<div class=\"wh-table-scroll\" tabindex=\"0\" role=\"region\" aria-label=\"Version-Specific Checks Before Updating to MariaDB 12.0\" style=\"width:100%;max-width:100%;overflow-x:auto;margin:28px 0;border:1px solid #dce5e9;border-radius:14px;background:#fff;box-shadow:0 10px 28px -16px rgba(24,47,60,.32);box-sizing:border-box\"><table style=\"width:100%;min-width:580px;border-collapse:separate;border-spacing:0;border:0;margin:0;font-size:15px;line-height:1.6;background:#fff\"><caption style=\"padding:20px;text-align:start;font-size:17px;line-height:1.5;font-weight:700;color:#173246;background:#fff\">Version-Specific Checks Before Updating to MariaDB 12.0<\/caption><thead><tr><th scope=\"col\" style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#19394d;color:#fff\">Checkpoint<\/th><th scope=\"col\" style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#19394d;color:#fff\">Why Is This Relevant?<\/th><th scope=\"col\" style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#19394d;color:#fff\">Test Method<\/th><th scope=\"col\" style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#19394d;color:#fff\">Area of Responsibility<\/th><\/tr><\/thead><tbody><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">my.cnf and linked files<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Removed or invalid options may interfere with startup<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Check the configuration inventory against the target version<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Database Operations<\/td><\/tr><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Removed variable `big_tables`<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">The variable was removed in MariaDB 12.0<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Identify occurrences in the main file and configuration fragments and clean them up before the update<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Database Operations<\/td><\/tr><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Removed the variable `large_page_size`<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">The variable was removed in MariaDB 12.0<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Identify occurrences in all loaded configuration files and evaluate the host configuration separately<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Database and Hosting Operations<\/td><\/tr><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Removed the variable `storage_engine`<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">The variable was removed in MariaDB 12.0<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Identify occurrences in the main file and configuration fragments and clean them up before the update<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#f4f7f9;color:#294252\">Database Operations<\/td><\/tr><tr><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Package Assembly<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Server, client, shared, and common packages must be compatible for the planned installation<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Check the planned package versions and package source before installation<\/td><td style=\"padding:15px 18px;border:0;border-bottom:1px solid #e2e9ed;text-align:start;vertical-align:top;white-space:normal;font-size:15px;line-height:1.6;background:#fff;color:#294252\">Package and Platform Management<\/td><\/tr><\/tbody><\/table><\/div><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">MariaDB 12.0 removes the system variables <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">big_tables<\/code>, <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">large_page_size<\/code> and <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">storage_engine<\/code>. Existing entries must therefore be in <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">my.cnf<\/code> and all associated configuration fragments must be found and evaluated for the target state. The cleanup must occur before the package update; in the case of <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">large_page_size<\/code> It is also important to distinguish between the removed MariaDB variable and the operating system's HugePages configuration, which is independent of it.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Package planning also deserves its own step: A repository can contain multiple MariaDB versions, and related server, client, shared, and common packages should be configured to match each other in version. The operating system version and package sources are part of the release. For host-level dependencies, the article on <a href=\"https:\/\/webhosting.de\/en\/linux-kernel-6-new-features-for-hosting-servers\/\">Relevant updates for hosting servers running the Linux 6.x kernel<\/a> additional context; however, it does not replace the database-specific staging check.  <\/p>\n<\/section><section class=\"wh-section\" aria-labelledby=\"abfragen-proxys-und-replikation\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"abfragen-proxys-und-replikation\" style=\"margin:38px 0 18px;color:#172f41;font-size:clamp(24px,1.25rem + 1vw,30px);font-weight:700;line-height:1.3;scroll-margin-top:115px\">Configure Special Cases Safely<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">For unstable reporting queries, troubleshooting should begin with execution plans, indexes, join conditions, and table statistics. Only once an undesirable plan has been reproducibly narrowed down can an optimizer hint serve as a targeted solution. The hint is specific to the query in question and should be included in a documented review, because data growth or changes in statistics can alter its effect later on.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Read-only queries are ideal for a risk-free assessment. Run them using an account that has only the necessary access permissions; they do not modify data, permissions, or server configuration. The results identify the database server that is actually connected and help verify assumptions made in deployment documentation.<\/p>\n<div class=\"wh-code-window\" data-wh-code style=\"margin:28px 0 34px;border:1px solid #2c4656;border-radius:12px;overflow:hidden;background:#132a3b;box-shadow:0 9px 25px -13px rgba(15,35,55,.2)\"><div class=\"wh-code-toolbar\" style=\"display:flex;flex-wrap:wrap;align-items:center;justify-content:space-between;gap:10px;padding:11px 16px;background:#223e50;color:#edf5fa;font-size:13px;line-height:1.5;font-weight:600\"><span>Code<\/span><button type=\"button\" class=\"wh-code-copy\" data-wh-copy hidden style=\"padding:6px 11px;border:1px solid #7893a1;border-radius:6px;background:transparent;color:#fff;font-size:12px;line-height:1.5;font-weight:600;cursor:pointer\">Copy code<\/button><span class=\"wh-copy-status\" aria-live=\"polite\"><\/span><span data-wh-copy-success hidden>Copied<\/span><span data-wh-copy-fallback hidden>Code highlighted\u2014please copy<\/span><\/div><pre class=\"wh-code\" data-no-translation translate=\"no\" style=\"display:block;margin:0;padding:20px;max-width:100%;overflow-x:auto;color:#edf5fa;background:#132a3b;font:14px\/1.75 ui-monospace,SFMono-Regular,Menlo,Consolas,monospace;white-space:pre;direction:ltr;text-align:left\"><code class=\"language-sql\" style=\"font:inherit;color:inherit;background:transparent;padding:0;border:0;white-space:inherit\">SELECT VERSION();\nSHOW VARIABLES LIKE &#039;max_open_cursors&#039;;\nSHOW VARIABLES LIKE &#039;create_tmp_table_binlog_formats&#039;;<\/code><\/pre><\/div><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">In a proxy architecture, <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">SET SESSION AUTHORIZATION<\/code> not a convenience feature, but an intervention in the security model. Switching sessions requires the privilege <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">SET USER<\/code> and is not available within transactions, prepared statements, or stored procedures.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Supported versions of MaxScale can use service credentials for the backend connection and then switch to the client's identity. This requires a MariaDB 12 or later backend server and the privilege <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">SET USER<\/code> required for the service account. However, this capability is not automatically provided by a MariaDB 12.0 backend alone: Before the rollout, the specific combination of MariaDB Server, MaxScale version, and configuration must be verified.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The MaxScale setting <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">use_service_credentials<\/code> In compatible versions, this setting determines whether MaxScale first logs in to the backend using the credentials stored in the service and then switches to the client identity. The service account must not be granted any administrative privileges beyond those technically necessary. Auditing and a documented emergency shutdown procedure must be compatible with the connection and pooling model.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Replication and Galera topologies require a dedicated test path for failover, rejoin, and recovery. Options for temporary tables or the handling of identical server IDs must not be changed without a thorough understanding of the binlog format, server ID, and return path. Furthermore, Galera optimization does not constitute a general performance guarantee for clusters, as load profiles and network latency remain critical factors.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Anyone evaluating internal tables, temporary structures, or storage engines in this environment should consider the role of each engine separately from the version migration. The article on <a href=\"https:\/\/webhosting.de\/en\/mariadb-aria-hosting-guide\/\">MariaDB Aria Storage Engine in Hosting<\/a> classifies such operational issues. However, the decisive factor in the decision to upgrade remains whether the specific application and its operational processes will function reproducibly on the target platform.<\/p>\n<\/section><section class=\"wh-section\" aria-labelledby=\"identitaetswechsel-und-audit\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"identitaetswechsel-und-audit\" style=\"margin:38px 0 18px;color:#172f41;font-size:clamp(24px,1.25rem + 1vw,30px);font-weight:700;line-height:1.3;scroll-margin-top:115px\">Ensuring Session Transition and Audit Security<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\"><code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">SET SESSION AUTHORIZATION<\/code> is a building block for intentionally designed connection architectures, not merely a convenience for administration. The command allows an authorized account to act under the identity of another user within the current session. The prerequisite is the privilege <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">SET USER<\/code>. This shifts responsibility for login and identity verification, at least in part, from individual customer accounts to a controlled platform component.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">This pattern may be useful for a proxy, but MariaDB Server and MaxScale remain separate products with their own versioning. Only MaxScale versions that support the use of service credentials followed by an identity switch can provide this workflow. A MariaDB 12.0 backend does not automatically extend an older or differently configured MaxScale branch with this capability.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">In a supported combination, the proxy logs in to the MariaDB server using the service account and then switches to the requested user identity. The setting <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">use_service_credentials<\/code> requires a MariaDB 12 or later backend server, as well as <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">SET USER<\/code> for the service account. Before implementation, the specific versions of MariaDB and MaxScale to be used, the configuration, and the intended authentication method must therefore be reviewed together.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The service account is useful because it allows you to <strong style=\"font-weight:700;color:inherit\">Identity changes are critical to security<\/strong>. The Privilege <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">SET USER<\/code> does not automatically grant it any global administrative privileges; furthermore, it may only be granted the permissions that are technically necessary. When switching sessions, account lockout, password expiration, authentication, and the REQUIRE-SSL check for the target account, among other things, can be bypassed. Furthermore, the switch is not available within transactions, prepared statements, or stored procedures.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">For multi-tenant hosting, this means: Customer accounts remain logically separated, and the permitted scope of changes is documented and limited. In addition, the platform requires an emergency shutdown mechanism, such as locking the service account or removing the affected connection path in accordance with a defined incident response procedure. The appropriate measure must be determined in consideration of connection pooling, existing sessions, and the impact on other clients.<\/p>\n<figure class=\"wp-block-image size-large wh-figure\" aria-describedby=\"wh-caption-detail2\" style=\"display:block;float:none;clear:both;width:100%;max-width:760px;margin:34px auto 40px;border:1px solid #dae5e9;border-radius:14px;overflow:hidden;background:#f5f8fa;box-shadow:0 10px 28px -17px rgba(24,47,60,.28);box-sizing:border-box\"><div class=\"wh-figure-media\" style=\"display:block;background:#eef3f5;line-height:0\"><img loading=\"lazy\" width=\"800\" height=\"534\" src=\"https:\/\/webhosting.de\/wp-content\/uploads\/2026\/09\/mariadb-proxy-audit-sicherheit-e0d29244-detail2-aec243bcac-1024x683.webp\" class=\"wp-image-21776\" alt=\"Network Access and Auditing as Part of a Secure Database Platform\" decoding=\"async\" srcset=\"https:\/\/webhosting.de\/wp-content\/uploads\/2026\/09\/mariadb-proxy-audit-sicherheit-e0d29244-detail2-aec243bcac-1024x683.webp 1024w, https:\/\/webhosting.de\/wp-content\/uploads\/2026\/09\/mariadb-proxy-audit-sicherheit-e0d29244-detail2-aec243bcac-300x200.webp 300w, https:\/\/webhosting.de\/wp-content\/uploads\/2026\/09\/mariadb-proxy-audit-sicherheit-e0d29244-detail2-aec243bcac-768x512.webp 768w, https:\/\/webhosting.de\/wp-content\/uploads\/2026\/09\/mariadb-proxy-audit-sicherheit-e0d29244-detail2-aec243bcac-18x12.webp 18w, https:\/\/webhosting.de\/wp-content\/uploads\/2026\/09\/mariadb-proxy-audit-sicherheit-e0d29244-detail2-aec243bcac.webp 1536w\" sizes=\"auto, (max-width: 800px) 100vw, 800px\" ><\/div><figcaption class=\"wh-caption\" id=\"wh-caption-detail2\" style=\"display:block;margin:0;padding:12px 18px 15px;border-top:1px solid #dce5e9;color:#506575;background:#f5f8fa;font-size:14px;line-height:1.55;text-align:start\">AI-generated stock image: Proxy access and audit data require a coordinated security and operational model.<\/figcaption><\/figure><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">In MariaDB 12.0, the Audit plugin adds the host, port, and TLS version used to incoming connections. This information helps better identify access attempts originating from behind NAT, load balancers, or proxies. However, they do not replace a reliable identification if an upstream system modifies source information or only passes its own address to the database server.  <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">It takes effect <strong style=\"font-weight:700;color:inherit\">Auditing<\/strong> First, an operational process must be established: Logs should be collected centrally, protected against unauthorized modification, and managed in accordance with a specified retention period. Access rights for viewing and exporting must be separated, as must responsibility for alerting and investigation. Whether additional log data noticeably affects the capacity or performance of a specific platform cannot be determined from the version alone without measurement.<\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">In the event of a security incident, operators should be able to determine which identity the proxy assigned, through which access point the session was established, and what audit data is available regarding it. Regular, documented checks of system shutdowns and log availability are more important than logging as extensively as possible. In particular, an audit log must not be used as a substitute for a rights management policy, transport encryption, or secure secret management.<\/p>\n<\/section><section class=\"wh-section\" aria-labelledby=\"betrieb-und-fehlersuche\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"betrieb-und-fehlersuche\" style=\"margin:38px 0 18px;color:#172f41;font-size:clamp(24px,1.25rem + 1vw,30px);font-weight:700;line-height:1.3;scroll-margin-top:115px\">Monitor Operation After the Upgrade<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">After a MariaDB update, an observation phase begins; there is no automatic optimization. First, you need to determine whether the <strong style=\"font-weight:700;color:inherit\">Server Startup<\/strong> fails, an application can no longer establish a connection, or a replication path diverges. These error scenarios have different causes and require separate solutions rather than being addressed with blanket configuration changes.<\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Startup errors are narrowed down using the server error log and a versioned inventory of the configuration files that were actually loaded. In MariaDB 12.0, for example, <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">big_tables<\/code> and <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">storage_engine<\/code> removed. Such entries must not be left unchanged in <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">my.cnf<\/code> or embedded configuration fragments; the documented variable reference and the startup message indicate which specific setting is affected. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">For connectors and plugins, you must record the installed packages, the loaded module versions, and the application's error message. Selecting a repository alone does not guarantee a compatible installation: When using a specific server version, server, client, shared, and common packages must be planned with matching versions. The available names and versions depend on the repository and operating system used. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Application errors are best investigated using a reproducible, as small as possible SQL test case and the corresponding client or connector logs. A read-only assessment can be performed using <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">SELECT VERSION();<\/code> begin. The result identifies the responding database server, but does not prove either the compatibility of an ORM or the correct operation of an application configuration.<\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">For replication, the diagnostic file should include the documented replication status, binlog format, server IDs, and events related to failover and rejoin. Temporary tables, the topology, and changes to replication options must be checked separately. A successful local write test is not sufficient to verify consistency and expected behavior across all involved instances.<\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Server and audit logs, configuration inventory, version queries, and reproducible query tests together provide a <strong style=\"font-weight:700;color:inherit\">traceable chain of errors<\/strong>. It also makes it easier to decide whether a fallback plan needs to be triggered. A higher version number does not necessarily result in a specific performance effect or universal tuning; changes to memory, optimizer, or replication parameters require a specific hypothesis and a verifiable effect.<\/p>\n<\/section><section class=\"wh-section\" aria-labelledby=\"entscheidung-fuer-plattformen\" style=\"display:block;margin:0 0 36px;min-width:0\"><h2 id=\"entscheidung-fuer-plattformen\" style=\"margin:38px 0 18px;color:#172f41;font-size:clamp(24px,1.25rem + 1vw,30px);font-weight:700;line-height:1.3;scroll-margin-top:115px\">Strategically Determine the Target Score<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The appropriate target version depends on the platform\u2019s purpose and operating model, not on the umbrella term \u201cMariaDB 12.\u201d For traditional CMS, e-commerce, and web application databases, upgrade reliability, clean tenant isolation, and a robust recovery path usually take precedence over individual new SQL features. New GIS functions or routines are not a reason for migration in and of themselves if the applications do not use them. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Complex reporting applications can benefit from optimizer hints when an analysis clearly identifies an undesirable execution plan. Before doing so, you should check indexes, join conditions, data distribution, and statistics. A hint is a specific constraint on an execution plan decision and may become inappropriate following data growth or changes to statistics; it should therefore be included in the application documentation along with the query, rationale, and criteria for revoking it. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Proxy and cluster environments require a separate test path. For a proxy, this specifically involves the service account\u2019s authorization model, session switches, and auditability. For replication or Galera, this includes failover, rejoin, restore, and the behavior of temporary tables. A successful upgrade of a single instance does not prove that these processes function correctly throughout the entire topology. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The <strong style=\"font-weight:700;color:inherit\">Release Strategy<\/strong> must evaluate Innovation Releases and LTS separately. MariaDB describes Innovation Releases as rolling releases that, as a rule, are not continuously maintained with patch versions after GA; the intended path leads to the next rolling series. LTS releases, on the other hand, are maintained for three years after GA. This does not imply a blanket commitment to package or contractual support for a specific hosting environment. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Before making a decision, therefore, the distribution\u2019s package and support landscape, tested application compatibility, a proven restore process, the security model, and ongoing operational costs must all be evaluated together. Despite many shared SQL patterns, MariaDB and MySQL are not interchangeable: MariaDB uses its own GTID model and, for example, does not support MySQL\u2019s <code data-no-translation style=\"font:600 .87em\/1.5 ui-monospace,monospace;color:#235063;background:#edf3f5;border-radius:4px;padding:.1em .3em\">SET PERSIST<\/code>. Migration assumptions based on a MySQL environment must therefore be verified. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">For the 12.0 series, 12.0.2 is documented as the stable GA release, while 12.0.0 was a preview and 12.0.1 was a release candidate. This classification describes the maturity status at that time but does not replace a current release decision. Immediately prior to rollout or release, operators must verify the offered package version, operating system support, and current release classification against the manufacturer\u2019s information. <\/p>\n<p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">The key factor, therefore, is the specific, tested platform version, along with its dependencies and operating rules. A controlled rollout is justified if compatibility, fallback plans, and responsibilities have been verifiably prepared. If these prerequisites are missing, the name \u201cMariaDB 12\u201d is not a reason to take on risks in shared hosting or in a business-critical database environment.<\/p>\n<\/section><section class=\"wh-sources\" style=\"margin:40px 0 0;padding:24px 0 0;border-top:1px solid #dce5e9;color:#596b7b;font-size:14px;line-height:1.65\"><h2 style=\"margin:38px 0 18px;color:#172f41;font-size:clamp(24px,1.25rem + 1vw,30px);font-weight:700;line-height:1.3;scroll-margin-top:115px\">Sources and Current State of Knowledge<\/h2><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Status of the research: <time datetime=\"2026-09-30\">2026-09-30<\/time><\/p><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\">Date of research: September 30, 2026. This article covers MariaDB Community Server 12.0; 12.0.0 was a preview, 12.0.1 was a release candidate, and 12.0.2 was documented as stable\/GA. Package offerings, operating system support, release classification, and contractual support commitments must be re-evaluated immediately prior to a rollout.<\/p><div class=\"wh-source-urls\"><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\"><span class=\"wh-source-url\" data-no-translation dir=\"ltr\" style=\"overflow-wrap:anywhere;font:12px\/1.6 ui-monospace,monospace;direction:ltr\">https:\/\/mariadb.com\/docs\/release-notes\/community-server\/old-releases\/12.0\/what-is-mariadb-120<\/span><\/p><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\"><span class=\"wh-source-url\" data-no-translation dir=\"ltr\" style=\"overflow-wrap:anywhere;font:12px\/1.6 ui-monospace,monospace;direction:ltr\">https:\/\/mariadb.com\/docs\/release-notes\/community-server\/about\/release-model<\/span><\/p><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\"><span class=\"wh-source-url\" data-no-translation dir=\"ltr\" style=\"overflow-wrap:anywhere;font:12px\/1.6 ui-monospace,monospace;direction:ltr\">https:\/\/mariadb.com\/docs\/release-notes\/community-server\/changelogs\/12.0\/12.0.2<\/span><\/p><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\"><span class=\"wh-source-url\" data-no-translation dir=\"ltr\" style=\"overflow-wrap:anywhere;font:12px\/1.6 ui-monospace,monospace;direction:ltr\">https:\/\/mariadb.com\/docs\/release-notes\/community-server\/about\/compatibility-and-differences\/incompatibilities-and-feature-differences-between-mariadb-rolling-and-mysql<\/span><\/p><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\"><span class=\"wh-source-url\" data-no-translation dir=\"ltr\" style=\"overflow-wrap:anywhere;font:12px\/1.6 ui-monospace,monospace;direction:ltr\">https:\/\/mariadb.com\/docs\/server\/server-management\/install-and-upgrade-mariadb\/installing-mariadb\/binary-packages\/rpm\/yum<\/span><\/p><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\"><span class=\"wh-source-url\" data-no-translation dir=\"ltr\" style=\"overflow-wrap:anywhere;font:12px\/1.6 ui-monospace,monospace;direction:ltr\">https:\/\/mariadb.com\/docs\/server\/reference\/sql-statements\/account-management-sql-statements\/set-session-authorization<\/span><\/p><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\"><span class=\"wh-source-url\" data-no-translation dir=\"ltr\" style=\"overflow-wrap:anywhere;font:12px\/1.6 ui-monospace,monospace;direction:ltr\">https:\/\/mariadb.com\/docs\/maxscale\/reference\/maxscale-servers<\/span><\/p><p style=\"margin:0 0 1.1em;font-size:inherit;line-height:inherit\"><span class=\"wh-source-url\" data-no-translation dir=\"ltr\" style=\"overflow-wrap:anywhere;font:12px\/1.6 ui-monospace,monospace;direction:ltr\">https:\/\/mariadb.com\/docs\/server\/server-management\/variables-and-modes\/server-system-variables<\/span><\/p><\/div><\/section><\/div>","protected":false},"excerpt":{"rendered":"<p>MariaDB 12.0 introduces new optimizer, audit, replication, and security features. For hosting platforms, however, a controlled update path is of paramount importance: the release model, package version, configuration, applications, and fallback must all be compatible.<\/p>","protected":false},"author":1,"featured_media":21774,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":""},"categories":[781],"tags":[],"class_list":["post-21770","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-datenbanken-administration-anleitungen"],"acf":[],"_links":{"self":[{"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/posts\/21770","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/comments?post=21770"}],"version-history":[{"count":4,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/posts\/21770\/revisions"}],"predecessor-version":[{"id":21777,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/posts\/21770\/revisions\/21777"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/media\/21774"}],"wp:attachment":[{"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/media?parent=21770"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/categories?post=21770"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/tags?post=21770"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}