Contributing to this translation requires agreeing to its contributor agreement.
Zen

Translation

It is usually sufficient toEspecially on a system with a lot of writes to InnoDB tables you should set {innodb_log_file_size} to 25%% of the size of {innodb_buffer_pool_size}. A very big {innodb_log_file_size} slows downHowever the bigger this value, the longer the recovery time after awill be when database crash considerably. See also <a href="https://www.mysqlperformanceblog.com/2006/07/03/choosing-proper-innodb_log_file_size/">this Article</a>es, so this value should not be set much higher than 256 MiB. Please note however that you cannot simply change the value of this variable. You need to shutdown the server, remove the InnoDB log files, set the new value in my.cnf, start the server, then check the error logs if everything went fine. See also <a href="https://mysqldatabaseadministration.blogspot.com/2007/01/increase-innodblogfilesize-proper-way.html">this blog entry</a>
Especially on a system with a lot of writes to InnoDB tables you should set {innodb_log_file_size} to 25% of {innodb_buffer_pool_size}. However the bigger this value, the longer the recovery time will be when database crashes, so this value should not be set much higher than 256 MiB. Please note however that you cannot simply change the value of this variable. You need to shutdown the server, remove the InnoDB log files, set the new value in my.cnf, start the server, then check the error logs if everything went fine. See also <a href="https://mysqldatabaseadministration.blogspot.com/2007/01/increase-innodblogfilesize-proper-way.html">this blog entry</a>
778/6610 · 661

Contributing to this translation requires agreeing to its contributor agreement.

English Romanian Actions
You do not have InnoDB enabled.
Nu ai InnoDB activat.
InnoDB is usually the better choice for table engines.
De obicei, InnoDB este alegerea cea mai bună pentru motoare de tabele.
have_innodb is set to 'value'
have_innodb este setat la „valoare”
InnoDB log size
Dimensiune jurnal InnoDB
The InnoDB log file size is not an appropriate size, in relation to the InnoDB buffer pool.
Dimensiunea fișierului jurnal InnoDB nu este o dimensiune adecvată, în raport cu buffer pool InnoDB.
Especially on a system with a lot of writes to InnoDB tables you should set {innodb_log_file_size} to 25% of {innodb_buffer_pool_size}. However the bigger this value, the longer the recovery time will be when database crashes, so this value should not be set much higher than 256 MiB. Please note however that you cannot simply change the value of this variable. You need to shutdown the server, remove the InnoDB log files, set the new value in my.cnf, start the server, then check the error logs if everything went fine. See also <a href="https://mysqldatabaseadministration.blogspot.com/2007/01/increase-innodblogfilesize-proper-way.html">this blog entry</a>
De obicei, este suficientă setarea propietății {innodb_log_file_size} la 25%% din mărimea lui {innodb_buffer_pool_size}. O valoare foarte mare pentru {innodb_log_file_size} va încetini considerabil timpul de recuperare după o distrugere(eroare gravă) a unei baze de date. A se vedea de asemenea <a href="https://www.mysqlperformanceblog.com/2006/07/03/choosing-proper-innodb_log_file_size/">Articolul acesta</a>. Trebuie să se închidă server-ul, elimine fișierele InnoDB cu intrări, seteze valoarea nouă în my.cnf, pornească server-ul și apoi să se verifice intrările de erori, pentru a se asigura că totul a decurs bine. A se vedea de asemenea <a href="https://mysqldatabaseadministration.blogspot.com/2007/01/increase-innodblogfilesize-proper-way.html">acest post din blog</a>
Your InnoDB log size is at %s%% in relation to the InnoDB buffer pool size, it should not be below 20%%
Dimensiunea jurnalului tău InnoDB este de %s%% în raport cu dimensiunea buffer pool InnoDB, nu ar trebui să fie sub 20%%
Max InnoDB log size
Dimensiune maximă jurnal InnoDB
The InnoDB log file size is inadequately large.
Dimensiunea fișierului jurnal InnoDB este insuficient de mare.
It is usually sufficient to set {innodb_log_file_size} to 25% of the size of {innodb_buffer_pool_size}. A very big {innodb_log_file_size} slows down the recovery time after a database crash considerably. See also <a href="https://www.percona.com/blog/2006/07/03/choosing-proper-innodb_log_file_size/">this Article</a>. You need to shutdown the server, remove the InnoDB log files, set the new value in my.cnf, start the server, then check the error logs if everything went fine. See also <a href="https://mysqldatabaseadministration.blogspot.com/2007/01/increase-innodblogfilesize-proper-way.html">this blog entry</a>
De obicei, este suficientă setarea propietății {innodb_log_file_size} la 25%% din mărimea lui {innodb_buffer_pool_size}. O valoare foarte mare pentru {innodb_log_file_size} va încetini considerabil timpul de recuperare după o distrugere(eroare gravă) a unei baze de date. A se vedea de asemenea <a href="https://www.mysqlperformanceblog.com/2006/07/03/choosing-proper-innodb_log_file_size/">Articolul acesta</a>. Trebuie să se închidă server-ul, elimine fișierele InnoDB cu intrări, seteze valoarea nouă în my.cnf, pornească server-ul și apoi să se verifice intrările de erori, pentru a se asigura că totul a decurs bine. A se vedea de asemenea <a href="https://mysqldatabaseadministration.blogspot.com/2007/01/increase-innodblogfilesize-proper-way.html">acest post din blog</a>
Your absolute InnoDB log size is %s MiB
Dimensiunea absolută a jurnalului tău InnoDB este de %s MiO

Loading…

User avatar liviuconcioiu

Marked for edit

  1. phpMyAdmin
  2. 5.2
  3. Romanian
Especially on a system with a lot of writes to InnoDB tables you should set {innodb_log_file_size} to 25% of {innodb_buffer_pool_size}. However the bigger this value, the longer the recovery time will be when database crashes, so this value should not be set much higher than 256 MiB. Please note however that you cannot simply change the value of this variable. You need to shutdown the server, remove the InnoDB log files, set the new value in my.cnf, start the server, then check the error logs if everything went fine. See also <a href="https://mysqldatabaseadministration.blogspot.com/2007/01/increase-innodblogfilesize-proper-way.html">this blog entry</a>
De obicei, este suficientă setarea propietății {innodb_log_file_size} la 25%% din mărimea lui {innodb_buffer_pool_size}. O valoare foarte mare pentru {innodb_log_file_size} va încetini considerabil timpul de recuperare după o distrugere(eroare gravă) a unei baze de date. A se vedea de asemenea <a href="https://www.mysqlperformanceblog.com/2006/07/03/choosing-proper-innodb_log_file_size/">Articolul acesta</a>. Trebuie să se închidă server-ul, elimine fișierele InnoDB cu intrări, seteze valoarea nouă în my.cnf, pornească server-ul și apoi să se verifice intrările de erori, pentru a se asigura că totul a decurs bine. A se vedea de asemenea <a href="https://mysqldatabaseadministration.blogspot.com/2007/01/increase-innodblogfilesize-proper-way.html">acest post din blog</a>
2 years ago
User avatar None

String updated in the repository

  1. phpMyAdmin
  2. 5.2
  3. Romanian
Especially on a system with a lot of writes to InnoDB tables you should set {innodb_log_file_size} to 25% of {innodb_buffer_pool_size}. However the bigger this value, the longer the recovery time will be when database crashes, so this value should not be set much higher than 256 MiB. Please note however that you cannot simply change the value of this variable. You need to shutdown the server, remove the InnoDB log files, set the new value in my.cnf, start the server, then check the error logs if everything went fine. See also <a href="https://mysqldatabaseadministration.blogspot.com/2007/01/increase-innodblogfilesize-proper-way.html">this blog entry</a>
De obicei, este suficientă setarea propietății {innodb_log_file_size} la 25%% din mărimea lui {innodb_buffer_pool_size}. O valoare foarte mare pentru {innodb_log_file_size} va încetini considerabil timpul de recuperare după o distrugere(eroare gravă) a unei baze de date. A se vedea de asemenea <a href="https://www.mysqlperformanceblog.com/2006/07/03/choosing-proper-innodb_log_file_size/">Articolul acesta</a>. Trebuie să se închidă server-ul, elimine fișierele InnoDB cu intrări, seteze valoarea nouă în my.cnf, pornească server-ul și apoi să se verifice intrările de erori, pentru a se asigura că totul a decurs bine. A se vedea de asemenea <a href="https://mysqldatabaseadministration.blogspot.com/2007/01/increase-innodblogfilesize-proper-way.html">acest post din blog</a>
2 years ago
User avatar None

Source string changed

  1. phpMyAdmin
  2. 5.2
  3. Romanian
It is usually sufficient toEspecially on a system with a lot of writes to InnoDB tables you should set {innodb_log_file_size} to 25%% of the size of {innodb_buffer_pool_size}. A very big {innodb_log_file_size} slows downHowever the bigger this value, the longer the recovery time after awill be when database crash considerably. See also <a href="https://www.mysqlperformanceblog.com/2006/07/03/choosing-proper-innodb_log_file_size/">this Article</a>es, so this value should not be set much higher than 256 MiB. Please note however that you cannot simply change the value of this variable. You need to shutdown the server, remove the InnoDB log files, set the new value in my.cnf, start the server, then check the error logs if everything went fine. See also <a href="https://mysqldatabaseadministration.blogspot.com/2007/01/increase-innodblogfilesize-proper-way.html">this blog entry</a>
2 years ago
Browse all string changes

Things to check

XML markup

XML tags in translation do not match source

Reset

Glossary

English Romanian
log phpMyAdmin

String information

Flags
no-php-format
Source string location
libraries/advisory_rules_generic.php:615 • libraries/advisory_rules_generic.php:642
String age
2 years ago
Last updated
12 months ago
Source string age
2 years ago
Translation file
po/ro.po, string 156