gian/phpmyadmin
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Translation update done using Pootle.

Browse Source
This commit is contained in:
Rouslan Placella 2012-01-15 19:35:36 +02:00 committed by Pootle server
parent c7e97232b4
commit 70229f9626
1 changed files with 12 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
po/it.po
View File

@ -5,7 +5,7 @@ msgstr ""
"Report-Msgid-Bugs-To: phpmyadmin-devel@lists.sourceforge.net\n"
"POT-Creation-Date: 2012-01-11 13:40+0100\n"
"PO-Revision-Date: 2012-01-15 19:35+0200\n"
"Last-Translator: any anonymous user <>\n"
"Last-Translator: Rouslan Placella <rouslan@placella.com>\n"
"Language-Team: italian <it@li.org>\n"
"Language: it\n"
"MIME-Version: 1.0\n"
@ -13325,6 +13325,17 @@ msgid ""
"mysqldatabaseadministration.blogspot.com/2007/01/increase-innodblogfilesize-"
"proper-way.html\">this blog entry</a>"
msgstr ""
"Solitamente è sufficiente impostare innodb_log_file_size al 25%% di "
"{innodb_buffer_pool_size}. Un innodb_log_file_size molto grande rallenta "
"considerevolmente il tempo di ripristino in seguito ad un crash del "
"database. Vedere anche <a "
"href=\"http://www.mysqlperformanceblog.com/2006/07/03/choosing-proper-"
"innodb_log_file_size/\">questo articolo</a>. È necessario fermare il server, "
"rimuovere i file log InnoDB, impostare il nuovo valore in my.cnf, avviare il "
"server, quindi controllare nei log degli errori se tutto è andato "
"correttamente. Consultare anche <a "
"href=\"http://mysqldatabaseadministration.blogspot.com/2007/01/increase-"
"innodblogfilesize-proper-way.html\">questo articolo di blog</a>."
#: po/advisory_rules.php:263
#, php-format