{"id":2982,"date":"2026-07-11T12:44:24","date_gmt":"2026-07-11T12:44:24","guid":{"rendered":"https:\/\/www.serverspan.com\/blog\/"},"modified":"2026-07-11T13:25:19","modified_gmt":"2026-07-11T13:25:19","slug":"mariadb-11-8-wordpress-upgrade-sau-ramai-pe-11-4","status":"publish","type":"post","link":"https:\/\/www.serverspan.ro\/blog\/mariadb-11-8-wordpress-upgrade-sau-ramai-pe-11-4\/","title":{"rendered":"MariaDB 11.8 WordPress: upgrade sau r\u0103m\u00e2i pe 11.4?"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\"><strong>P\u0103streaz\u0103 MariaDB 11.4 pe majoritatea serverelor WordPress \u0219i WooCommerce existente care func\u021bioneaz\u0103 stabil.<\/strong> Treci la MariaDB 11.8 atunci c\u00e2nd construie\u0219ti un server nou, c\u00e2nd sistemul de operare sau panoul de control \u00eel accept\u0103 oficial ori c\u00e2nd o func\u021bie din 11.8 rezolv\u0103 o problem\u0103 demonstrat\u0103. MariaDB 11.8 este LTS, dar mentenan\u021ba versiunii Community se \u00eencheie \u00een iunie 2028, \u00een timp ce MariaDB 11.4 r\u0103m\u00e2ne \u00eentre\u021binut p\u00e2n\u0103 \u00een mai 2029. Ambele dep\u0103\u0219esc cerin\u021bele oficiale WordPress \u0219i WooCommerce. O versiune mai nou\u0103 nu \u00eenseamn\u0103 automat un magazin mai rapid.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Scris de echipa tehnic\u0103 ServerSpan<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Faptul c\u0103 MariaDB 11.8 este LTS nu reprezint\u0103 un motiv pentru abandonarea versiunii 11.4<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Eticheta LTS arat\u0103 c\u0103 MariaDB 11.8 prime\u0219te mentenan\u021b\u0103 pe termen lung. Nu \u00eenseamn\u0103 c\u0103 are o perioad\u0103 de suport Community mai lung\u0103 dec\u00e2t fiecare versiune LTS anterioar\u0103.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><a rel=\"nofollow\" href=\"https:\/\/mariadb.org\/about\/#maintenance-policy\">Politica de mentenan\u021b\u0103 MariaDB Foundation<\/a> listeaz\u0103 mentenan\u021ba Community pentru MariaDB 11.8 p\u00e2n\u0103 la 4 iunie 2028. MariaDB 11.4 r\u0103m\u00e2ne \u00eentre\u021binut p\u00e2n\u0103 la 29 mai 2029, deoarece versiunile p\u00e2n\u0103 la 11.4 au fost acoperite de politica anterioar\u0103, care oferea cinci ani de mentenan\u021b\u0103 pentru binarele Community.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Aceast\u0103 situa\u021bie r\u0103stoarn\u0103 presupunerea obi\u0219nuit\u0103. Trecerea de la 11.4 la 11.8 ofer\u0103 func\u021bii mai noi, dar scurteaz\u0103 cu aproximativ un an perioada de mentenan\u021b\u0103 Community publicat\u0103 \u00een prezent.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Factor de decizie<\/th><th>R\u0103m\u00e2i pe MariaDB 11.4<\/th><th>Treci la MariaDB 11.8<\/th><\/tr><\/thead><tbody><tr><td>Compatibilitate WordPress<\/td><td>Respect\u0103 recomandarea MariaDB 10.11 sau mai nou<\/td><td>Respect\u0103 recomandarea MariaDB 10.11 sau mai nou<\/td><\/tr><tr><td>Compatibilitate WooCommerce<\/td><td>Dep\u0103\u0219e\u0219te recomandarea MariaDB 10.6 sau mai nou<\/td><td>Dep\u0103\u0219e\u0219te recomandarea MariaDB 10.6 sau mai nou<\/td><\/tr><tr><td>Mentenan\u021b\u0103 Community<\/td><td>P\u00e2n\u0103 la 29 mai 2029<\/td><td>P\u00e2n\u0103 la 4 iunie 2028<\/td><\/tr><tr><td>Maturitate opera\u021bional\u0103<\/td><td>Istoric mai lung \u00een produc\u021bie \u0219i mai pu\u021bine variabile noi<\/td><td>Comportament mai nou al optimizatorului \u0219i valori implicite diferite<\/td><\/tr><tr><td>Performan\u021b\u0103<\/td><td>Comportament deja cunoscut pentru workload-ul existent<\/td><td>Posibile \u00eembun\u0103t\u0103\u021biri pentru anumite query-uri, care trebuie testate<\/td><\/tr><tr><td>Risc de upgrade<\/td><td>Nu este necesar\u0103 migrarea bazei de date<\/td><td>Necesit\u0103 testarea pachetelor, configura\u021biei, SQL-ului din plugin-uri \u0219i procedurii de rollback<\/td><\/tr><tr><td>Scenariul potrivit<\/td><td>Server WordPress sau WooCommerce existent \u0219i stabil<\/td><td>Instal\u0103ri noi, rebuild-uri planificate sau workload-uri care beneficiaz\u0103 demonstrabil de o schimbare din 11.8<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 ai nevoie de un audit al configura\u021biei bazei de date \u00eenainte de aceast\u0103 decizie, serviciul ServerSpan de <a href=\"https:\/\/www.serverspan.ro\/linux-administration\">administrare servere Linux<\/a> acoper\u0103 configurarea MariaDB, optimizarea bazelor de date, depanarea upgrade-urilor, recuperarea din backup \u0219i lucr\u0103rile de replicare.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">WordPress \u0219i WooCommerce accept\u0103 ambele versiuni<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Compatibilitatea cu WordPress core nu este factorul care decide \u00eentre MariaDB 11.4 \u0219i 11.8. <a rel=\"nofollow\" href=\"https:\/\/wordpress.org\/about\/requirements\/\">Cerin\u021bele oficiale WordPress<\/a> recomand\u0103 MariaDB 10.11 sau o versiune mai nou\u0103. <a rel=\"nofollow\" href=\"https:\/\/woocommerce.com\/document\/server-requirements\/\">Recomand\u0103rile oficiale WooCommerce pentru server<\/a> accept\u0103 MariaDB 10.6 sau o versiune mai nou\u0103.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">At\u00e2t 11.4, c\u00e2t \u0219i 11.8 dep\u0103\u0219esc aceste cerin\u021be. O instalare WordPress standard care folose\u0219te driverul PHP obi\u0219nuit pentru baze de date ar trebui s\u0103 se conecteze la oricare dintre versiuni f\u0103r\u0103 modific\u0103ri ale aplica\u021biei.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Riscul real de compatibilitate se afl\u0103 \u00een afara WordPress core. Plugin-urile custom pot crea propriile tabele, pot executa SQL neobi\u0219nuit, pot presupune existen\u021ba unui anumit collation sau pot depinde de un panou de control care administreaz\u0103 pachetele MariaDB prin propriile repository-uri \u0219i propriul sistem de configurare.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Verific\u0103 mediul real \u00eenainte de a lua decizia:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>mariadb --version\n\nsudo mariadb -NBe \"\nSELECT\n  @@version,\n  @@version_comment,\n  @@character_set_server,\n  @@collation_server,\n  @@sql_mode;\n\"<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Prima comand\u0103 confirm\u0103 versiunea clientului instalat. Query-ul SQL confirm\u0103 versiunea serverului care ruleaz\u0103 \u0219i valorile sale implicite active. Dac\u0103 serverul \u0219i clientul provin din familii diferite de pachete sau versiunea raportat\u0103 difer\u0103 de cea afi\u0219at\u0103 de panoul de control, rezolv\u0103 aceast\u0103 neconcordan\u021b\u0103 \u00eenainte de planificarea upgrade-ului.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">MariaDB 11.8 nu face automat WooCommerce mai rapid<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">MariaDB 11.8 con\u021bine \u00eembun\u0103t\u0103\u021biri reale pentru optimizator \u0219i InnoDB. Documenta\u021bia versiunii listeaz\u0103 decizii mai bune bazate pe cost pentru anumite query-uri de actualizare \u0219i \u0219tergere, suport suplimentar pentru expresii, \u00eembun\u0103t\u0103\u021biri ale index condition pushdown pentru tabele parti\u021bionate \u0219i lucr\u0103ri de scalabilitate pentru adaptive hash index din InnoDB.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Niciuna dintre aceste schimb\u0103ri nu garanteaz\u0103 \u00eenc\u0103rcarea mai rapid\u0103 a paginii de produs, a co\u0219ului, a checkout-ului sau a zonei de administrare. O cerere WooCommerce poate consuma timpul \u00een PHP, API-uri externe, rat\u0103ri ale object cache-ului, un tabel de plugin f\u0103r\u0103 indexuri potrivite sau query-uri repetate asupra unor tabele mari de metadate. Actualizarea motorului bazei de date nu repar\u0103 un query prost sau un buffer pool subdimensionat.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Documenta\u021bia MariaDB pentru upgrade-uri \u00eentre versiuni majore precizeaz\u0103 c\u0103 \u00eembun\u0103t\u0103\u021birile optimizatorului ar trebui s\u0103 ajute \u00een mod normal, dar admite \u0219i posibilitatea unor regresii rare ale planurilor de execu\u021bie. Testul corect este workload-ul t\u0103u, nu un benchmark generic.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cenregistreaz\u0103 configura\u021bia slow query log \u00eenainte de testare:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo mariadb -NBe \"\nSHOW VARIABLES\nWHERE Variable_name IN (\n  'slow_query_log',\n  'slow_query_log_file',\n  'long_query_time'\n);\n\"<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Un rezultat util arat\u0103 c\u0103 slow query log este activ, identific\u0103 o cale de log \u00een care serverul poate scrie \u0219i afi\u0219eaz\u0103 un prag potrivit investiga\u021biei. Dac\u0103 logul este dezactivat, activeaz\u0103-l mai \u00eent\u00e2i \u00een staging sau pe durata unei perioade controlate de observa\u021bie. Nu p\u0103stra logarea agresiv\u0103 activ\u0103 permanent pe un magazin de produc\u021bie aglomerat f\u0103r\u0103 s\u0103 urm\u0103re\u0219ti spa\u021biul ocupat pe disc.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Compar\u0103 acela\u0219i proces de checkout, filtrarea produselor, joburile programate, importurile \u0219i rapoartele administrative pe 11.4 \u0219i 11.8. Verific\u0103 durata query-urilor \u0219i planurile de execu\u021bie cu <code>EXPLAIN<\/code>. P\u0103streaz\u0103 aceea\u0219i versiune PHP, acela\u0219i con\u021binut al object cache-ului, acela\u0219i set de date \u0219i aceea\u0219i configura\u021bie a bazei de date \u00een timpul compara\u021biei.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Pentru o analiz\u0103 mai larg\u0103 a blocajelor WooCommerce, vezi <a href=\"https:\/\/www.serverspan.ro\/blog\/magazinul-tau-woocommerce-s-a-prabusit-de-black-friday-iata-ce-trebuie-sa-faci-acum-pentru-urmatorul\/\">ce provoac\u0103 \u00een realitate c\u0103derea unui magazin WooCommerce \u00een perioadele cu trafic ridicat<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Noile valori implicite pentru charset conteaz\u0103 mai mult pentru plugin-uri dec\u00e2t pentru tabelele core existente<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">MariaDB 11.8 schimb\u0103 setul de caractere implicit al serverului de la <code>latin1<\/code> la <code>utf8mb4<\/code> \u0219i collation-ul Unicode implicit la <code>uca1400_ai_ci<\/code>. Este o valoare implicit\u0103 modern\u0103 mai bun\u0103 pentru obiectele noi ale bazei de date, dar nu reprezint\u0103 o comand\u0103 de convertire a tuturor tabelelor WordPress existente.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Tabelele existente \u00ee\u0219i p\u0103streaz\u0103 setul de caractere \u0219i collation-ul definite, dac\u0103 nu sunt modificate explicit. Tabelele noi create f\u0103r\u0103 set\u0103ri explicite pot mo\u0219teni valorile serverului. Plugin-urile WordPress scrise corect folosesc <code>$wpdb-&gt;get_charset_collate()<\/code> atunci c\u00e2nd creeaz\u0103 tabele, conform <a rel=\"nofollow\" href=\"https:\/\/developer.wordpress.org\/plugins\/creating-tables-with-plugins\/\">WordPress Plugin Handbook<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Verific\u0103 distribu\u021bia actual\u0103 \u00eenainte de upgrade:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo mariadb -NBe \"\nSELECT\n  TABLE_SCHEMA,\n  TABLE_COLLATION,\n  COUNT(*) AS tables_using_collation\nFROM information_schema.TABLES\nWHERE TABLE_SCHEMA NOT IN (\n  'mysql',\n  'information_schema',\n  'performance_schema',\n  'sys'\n)\nAND TABLE_TYPE = 'BASE TABLE'\nGROUP BY TABLE_SCHEMA, TABLE_COLLATION\nORDER BY TABLE_SCHEMA, TABLE_COLLATION;\n\"<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Un num\u0103r mic de collation-uri alese inten\u021bionat este normal. O baz\u0103 de date WordPress care con\u021bine mai multe combina\u021bii f\u0103r\u0103 leg\u0103tur\u0103 \u00eentre <code>utf8<\/code>, <code>utf8mb4<\/code> \u0219i collation-uri specifice unor vendori trebuie analizat\u0103, mai ales dac\u0103 sunt executate join-uri \u00eentre coloane text din tabelele mai multor plugin-uri.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Nu combina upgrade-ul MariaDB cu o conversie \u00een mas\u0103 a collation-urilor, dec\u00e2t dac\u0103 acea conversie are propriul plan testat. Separarea modific\u0103rilor face identificarea erorilor \u0219i rollback-ul mult mai simple.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Upgrade-ul direct de la 11.4 la 11.8 este acceptat<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">MariaDB public\u0103 un <a rel=\"nofollow\" href=\"https:\/\/mariadb.com\/docs\/server\/server-management\/install-and-upgrade-mariadb\/upgrading\/mariadb-community-server-upgrade-paths\/upgrading-from-mariadb-11-4-to-mariadb-11-8\">ghid dedicat upgrade-ului de la 11.4 la 11.8<\/a>. Succesiunea documentat\u0103 este s\u0103 creezi un backup, s\u0103 schimbi repository-ul pachetelor, s\u0103 opre\u0219ti MariaDB, s\u0103 \u00eenlocuie\u0219ti pachetele vechi ale serverului, s\u0103 verifici op\u021biunile de configurare, s\u0103 porne\u0219ti serverul nou \u0219i s\u0103 rulezi <code>mariadb-upgrade<\/code>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Lista de incompatibilit\u0103\u021bi specific\u0103 traseului 11.4 la 11.8 este scurt\u0103. Op\u021biunea eliminat\u0103 <code>wsrep_load_data_splitting<\/code> prive\u0219te \u00een principal mediile Galera. MariaDB nu listeaz\u0103 valori implicite modificate \u00een ghidul specific de upgrade, de\u0219i schimb\u0103rile cumulate din versiunile 11.5 p\u00e2n\u0103 la 11.8 afecteaz\u0103 obiectele noi ale bazei de date \u0219i comportamentul optimizatorului.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Lista scurt\u0103 de incompatibilit\u0103\u021bi nu transform\u0103 fereastra de mentenan\u021b\u0103 \u00eentr-un simplu update de pachete. Panourile de hosting pot administra propriile repository-uri, defini\u021bii de servicii, socket-uri, integr\u0103ri de backup sau workflow-uri CustomBuild. Ocolirea procedurii acceptate de panou poate l\u0103sa baza de date func\u021bional\u0103, \u00een timp ce panoul consider\u0103 c\u0103 este instalat\u0103 o alt\u0103 versiune.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 \u00eenc\u0103 migrezi de la MariaDB 10.6, cite\u0219te analiza despre <a href=\"https:\/\/www.serverspan.ro\/blog\/directadmin-legacy-license-iulie-2026-mariadb-10-6-eol-optiuni-migrare\/\">EOL-ul MariaDB 10.6 \u0219i op\u021biunile de migrare pentru DirectAdmin Legacy<\/a>. Pentru situa\u021bia neobi\u0219nuit\u0103 \u00een care DirectAdmin nu poate administra corect MariaDB 11.4 prin CustomBuild, consult\u0103 <a href=\"https:\/\/www.serverspan.ro\/blog\/tutorial-cum-sa-folosesti-mariadb-11-4-intr-un-mediu-directadmin-legacy-bazat-pe-debian-ca-un-sysadmin\/\">modelul de integrare manual\u0103 a MariaDB 11.4<\/a>. Acestea sunt probleme diferite de decizia privind trecerea unui server s\u0103n\u0103tos de la 11.4 la 11.8.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Reinstalarea versiunii 11.4 nu este un plan sigur de rollback<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">MariaDB este proiectat s\u0103 actualizeze fi\u0219ierele bazei de date \u00eenainte, c\u0103tre versiuni mai noi. Nu este proiectat pentru reinstalarea nepreg\u0103tit\u0103 a unor binare mai vechi peste un director de date care a fost deja deschis \u0219i actualizat de o versiune nou\u0103.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Un rollback real \u00eenseamn\u0103 una dintre urm\u0103toarele variante:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Restaurezi un backup verificat, creat \u00eenainte de upgrade, \u00eentr-un mediu MariaDB 11.4 curat.<\/li>\n\n\n\n<li>Mu\u021bi traficul \u00eenapoi c\u0103tre un server sau o replic\u0103 11.4 neatins\u0103, care a fost p\u0103strat\u0103 izolat\u0103 \u00een timpul upgrade-ului.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Un snapshot poate ajuta, dar numai dac\u0103 surprinde baza de date oprit\u0103 corect sau \u00eentr-o stare consistent\u0103 cu aplica\u021bia. Trebuie s\u0103 \u00een\u021belegi \u0219i c\u0103 revenirea la snapshot elimin\u0103 fiecare comand\u0103, actualizare de plat\u0103, modificare de client \u0219i ajustare de stoc scris\u0103 dup\u0103 momentul snapshot-ului.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Pentru WooCommerce, un rollback nepreg\u0103tit la snapshot este periculos. Magazinul poate p\u0103rea func\u021bional, de\u0219i baza de date a r\u0103mas \u00een urma procesatorului de pl\u0103\u021bi, a sistemului de fulfilment sau a sursei externe de stoc.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Folose\u0219te o copie de staging \u00eenainte de modificarea magazinului de produc\u021bie<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Cea mai bun\u0103 \u021bint\u0103 pentru validare este o copie recent\u0103 a bazei de date reale, restaurat\u0103 pe un server separat. O instalare WordPress goal\u0103 nu dovede\u0219te aproape nimic despre un magazin WooCommerce matur, cu plugin-uri custom \u0219i mai mul\u021bi ani de date despre comenzi.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cenainte de testare, ruleaz\u0103 urm\u0103toarele verific\u0103ri WordPress read-only sub utilizatorul site-ului, nu ca root:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>wp core verify-checksums\nwp db check\nwp plugin list --status=active\nwp db query \"SELECT VERSION();\"<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Un rezultat bun confirm\u0103 c\u0103 fi\u0219ierele WordPress core corespund checksum-urilor oficiale, tabelele trec verific\u0103rile de baz\u0103, plugin-urile active sunt inventariate \u0219i WordPress se conecteaz\u0103 la serverul MariaDB a\u0219teptat. Repar\u0103 orice corupere existent\u0103 sau modificare necunoscut\u0103 a fi\u0219ierelor core \u00eenainte de a atribui erorile ulterioare versiunii MariaDB 11.8.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dup\u0103 upgrade-ul din staging, testeaz\u0103 autentificarea, checkout-ul, ramburs\u0103rile, cupoanele, c\u0103utarea produselor, administrarea comenzilor, scheduled actions, importurile, exporturile, backupurile \u0219i rapoartele custom. Verific\u0103 logul serviciului MariaDB dup\u0103 upgrade:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo journalctl -u mariadb --since \"30 minutes ago\" --no-pager\nsudo mariadb-upgrade\nwp db check<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Logul nu trebuie s\u0103 con\u021bin\u0103 erori repetate despre op\u021biuni nesuportate, motoare de stocare, permisiuni sau crash recovery. Comanda <code>mariadb-upgrade<\/code> trebuie s\u0103 se \u00eencheie cu succes, iar verificarea final\u0103 a bazei de date WordPress trebuie s\u0103 treac\u0103.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Regula practic\u0103 de decizie<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>R\u0103m\u00e2i pe 11.4<\/strong> c\u00e2nd magazinul de produc\u021bie este stabil, complet actualizat, acceptat de panoul de control \u0219i nu ob\u021bine niciun beneficiu m\u0103surabil din 11.8.<\/li>\n\n\n\n<li><strong>Alege 11.8 pentru o instalare nou\u0103<\/strong> c\u00e2nd sistemul de operare \u0219i stack-ul de administrare \u00eel accept\u0103 nativ \u0219i nu exist\u0103 configura\u021bii legacy de transportat.<\/li>\n\n\n\n<li><strong>Actualizeaz\u0103 un magazin existent<\/strong> c\u00e2nd testele din staging trec, backupurile au fost restaurate cu succes \u0219i versiunea nou\u0103 rezolv\u0103 o cerin\u021b\u0103 opera\u021bional\u0103 concret\u0103.<\/li>\n\n\n\n<li><strong>Nu face upgrade doar pentru vitez\u0103<\/strong> p\u00e2n\u0103 c\u00e2nd acela\u0219i workload WooCommerce nu demonstreaz\u0103 o \u00eembun\u0103t\u0103\u021bire repetabil\u0103.<\/li>\n\n\n\n<li><strong>Nu face upgrade pentru o perioad\u0103 Community mai lung\u0103<\/strong>, deoarece data de \u00eencheiere a mentenan\u021bei publicat\u0103 pentru 11.4 este mai t\u00e2rzie dec\u00e2t cea pentru 11.8.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Pentru majoritatea serverelor WordPress \u0219i WooCommerce existente, MariaDB 11.4 r\u0103m\u00e2ne alegerea ra\u021bional\u0103 pentru produc\u021bie. MariaDB 11.8 este potrivit pentru instal\u0103ri noi \u0219i migr\u0103ri testate, dar eticheta LTS nu creeaz\u0103 o urgen\u021b\u0103, nu prelunge\u0219te perioada de mentenan\u021b\u0103 Community \u0219i nu garanteaz\u0103 query-uri de checkout mai rapide.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 upgrade-ul implic\u0103 un magazin de produc\u021bie, un panou de hosting sau o baz\u0103 de date prea mare pentru o restaurare improvizat\u0103, serviciul ServerSpan de <a href=\"https:\/\/www.serverspan.ro\/linux-administration\">administrare a bazelor de date pe Linux<\/a> poate acoperi verific\u0103rile de compatibilitate, configurarea MariaDB, validarea backupurilor, executarea upgrade-ului \u0219i depanarea de dup\u0103 migrare.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>P\u0103streaz\u0103 MariaDB 11.4 pe majoritatea serverelor WordPress \u0219i WooCommerce existente care func\u021bioneaz\u0103 stabil. Treci la MariaDB 11.8 atunci c\u00e2nd construie\u0219ti un server nou, c\u00e2nd sistemul de operare sau panoul de control \u00eel accept\u0103 oficial ori c\u00e2nd o func\u021bie din 11.8 rezolv\u0103 o problem\u0103 demonstrat\u0103. MariaDB 11.8 este LTS, dar mentenan\u021ba versiunii Community se \u00eencheie \u00een [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":2980,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[12],"tags":[17003,16995,16998,17000,17005,17001,16996,16964,16969,16971,16967,16978,16975,17007,1458,17008,16994,17004,16999,17002,17009,17006,17011,17012,16993,16997,17014,17010,17013],"class_list":["post-2982","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-virtual-servers","tag-backup-mariadb-inainte-de-upgrade","tag-cerinte-baza-de-date-woocommerce","tag-cerinte-mariadb-wordpress","tag-charset-implicit-mariadb-11-8","tag-checklist-upgrade-mariadb","tag-collation-baza-de-date-wordpress","tag-compatibilitate-mariadb-wordpress","tag-mariadb-11-8-vs-11-4","tag-mariadb-11-8-woocommerce","tag-mariadb-11-8-wordpress","tag-mariadb-lts-wordpress","tag-mariadb-uca1400_ai_ci","tag-mariadb-upgrade-wordpress","tag-migrare-baza-de-date-wordpress-2","tag-optimizare-baza-de-date-woocommerce","tag-optimizator-mariadb-wordpress","tag-performanta-mariadb-11-8","tag-query-uri-lente-woocommerce","tag-risc-downgrade-mariadb","tag-rollback-mariadb-11-8","tag-sfarsit-suport-mariadb-11-4","tag-sfarsit-suport-mariadb-11-8","tag-slow-query-log-mariadb","tag-testare-mariadb-in-staging","tag-upgrade-mariadb-11-4-la-11-8","tag-upgrade-mariadb-11-8","tag-upgrade-mariadb-administrat","tag-upgrade-mariadb-directadmin","tag-upgrade-repository-mariadb"],"_links":{"self":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2982","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2982"}],"version-history":[{"count":2,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2982\/revisions"}],"predecessor-version":[{"id":3024,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2982\/revisions\/3024"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/media\/2980"}],"wp:attachment":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2982"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2982"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2982"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}