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.percona.com/blog/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>
692/6610 · 661

Contributing to this translation requires agreeing to its contributor agreement.

English Bulgarian Actions
You do not have InnoDB enabled.
InnoDB е забранен.
InnoDB is usually the better choice for table engines.
Обикновено InnoDB е по-добър избор на хранилище.
have_innodb is set to 'value'
have_innodb е 'value'
InnoDB log size
Размер на дневника на InnoDB
The InnoDB log file size is not an appropriate size, in relation to the InnoDB buffer pool.
Размерът на лог-файла на InnoDB не съответства на буфера на 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>
Обикновено е достатъчно да се сложи {innodb_log_file_size} на 25%% от размера на {innodb_buffer_pool_size}. Много голямо {innodb_log_file_size} забавя значително времето за възстановяване след срив в базата данни. Вижте също <a href="https://www.percona.com/blog/2006/07/03/choosing-proper-innodb_log_file_size/"> тази статия </a>. Необходимо е да спрете сървъра, да премахнете InnoDB журналните файлове, да сложите нова стойновт във my.cnf, да стартирате сървъра, след това да проверите за грешки в журналните файлове и дали всичко е минало добре. Вижте също и<a href="https://mysqldatabaseadministration.blogspot.com/2007/01/increase-innodblogfilesize-proper-way.html"> тази блог статия</a>
Your InnoDB log size is at %s%% in relation to the InnoDB buffer pool size, it should not be below 20%%
Размерът на вашият лог-файл на InnoDB е %s%% от размера на буфера на InnoDB, това съотношение не трябва да е по-малко от 20%%
Max InnoDB log size
Максимален размер на дневника на InnoDB
The InnoDB log file size is inadequately large.
Лог-файла на InnoDB е неоправдано голям.
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>
Обикновено е достатъчно да се сложи {innodb_log_file_size} на 25%% от размера на {innodb_buffer_pool_size}. Много голямо {innodb_log_file_size} забавя значително времето за възстановяване след срив в базата данни. Вижте също <a href="https://www.percona.com/blog/2006/07/03/choosing-proper-innodb_log_file_size/"> тази статия </a>. Необходимо е да спрете сървъра, да премахнете InnoDB журналните файлове, да сложите нова стойновт във my.cnf, да стартирате сървъра, след това да проверите за грешки в журналните файлове и дали всичко е минало добре. Вижте също и<a href="https://mysqldatabaseadministration.blogspot.com/2007/01/increase-innodblogfilesize-proper-way.html"> тази блог статия</a>
Your absolute InnoDB log size is %s MiB
Абсолютният размер на InnoDB журналa е %s MiB

Loading…

User avatar None

String updated in the repository

  1. phpMyAdmin
  2. Development
  3. Bulgarian
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>
Обикновено е достатъчно да се сложи {innodb_log_file_size} на 25%% от размера на {innodb_buffer_pool_size}. Много голямо {innodb_log_file_size} забавя значително времето за възстановяване след срив в базата данни. Вижте също <a href="https://www.percona.com/blog/2006/07/03/choosing-proper-innodb_log_file_size/"> тази статия </a>. Необходимо е да спрете сървъра, да премахнете InnoDB журналните файлове, да сложите нова стойновт във my.cnf, да стартирате сървъра, след това да проверите за грешки в журналните файлове и дали всичко е минало добре. Вижте също и<a href="https://mysqldatabaseadministration.blogspot.com/2007/01/increase-innodblogfilesize-proper-way.html"> тази блог статия</a>
5 months ago
User avatar None

Source string changed

  1. phpMyAdmin
  2. Development
  3. Bulgarian
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.percona.com/blog/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>
5 months ago
Browse all string changes

Things to check

XML markup

XML tags in translation do not match source

Reset

Glossary

English Bulgarian
log phpMyAdmin

String information

Flags
ignore-php-format, no-php-format
Source string location
src/Advisory/Rules.php:650 • src/Advisory/Rules.php:680
String age
5 months ago
Last updated
a week ago
Source string age
3 years ago
Translation file
resources/po/bg.po, string 1426