View contributor agreement Contribution to this translation requires you to agree with a contributor agreement.

Translation status

3,351 Strings 100% Translate
22,218 Words 100%

Other components

Component Translated Untranslated Untranslated words Checks Suggestions Comments
Documentation GPL-3.0 96% 89 2,131 1 1
Debian GPL-2.0
SQL parser GPL-2.0 5
4.9 GPL-2.0 2
5.0 GPL-2.0 5

Translation Information

Project website www.phpmyadmin.net
Mailing list for translators translators@phpmyadmin.net
Instructions for translators

https://www.phpmyadmin.net/translate/

Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Translation license GNU General Public License v3.0 or later
Contributor agreement View
Repository https://github.com/phpmyadmin/phpmyadmin.git
Repository branch master
Last remote commit Merge pull request #16367 from mauriciofauth/central-columns b252406f8f
User avatar mauriciofauth authored 6 hours ago
Repository containing Weblate translations https://hosted.weblate.org/git/phpmyadmin/master/
Filemaskpo/*.po
Translation file po/pt_BR.po
User avatar None

Resource update

phpMyAdmin / DevelopmentPortuguese (Brazil)

Resource update 6 days ago
User avatar None

Resource update

phpMyAdmin / DevelopmentPortuguese (Brazil)

Resource update 3 weeks ago
(current)
(currentatual)
3 weeks ago
There is an issue with your request.
l10n: No caso de uma consulta SQL não passar por uma verificação de segurançaExiste um problema com a sua requisição.
3 weeks ago
Checksum
VSoma de verificarção
3 weeks ago
Maintenance operations on multiple tables are disabled.
Operações de manutenção em várias tabelas estão desabilitadas.
3 weeks ago
Less than 80% of the query cache is being utilized.
Menos de 80%% do cache de query está sendo utilizado.
3 weeks ago
Query cache efficiency (%)
Eficiência do cache de consulta (%%)
3 weeks ago
The InnoDB buffer pool has a profound impact on performance for InnoDB tables. Assign all your remaining memory to this buffer. For database servers that use solely InnoDB as storage engine and have no other services (e.g. a web server) running, you may set this as high as 80% of your available memory. If that is not the case, you need to carefully assess the memory consumption of your other services and non-InnoDB-Tables and set this variable accordingly. If it is set too high, your system will start swapping, which decreases performance significantly. See also <a href="https://www.percona.com/blog/2007/11/03/choosing-innodb_buffer_pool_size/">this article</a>
O buffer pool do InnoDB possui um profundo impacto na performance de tabelas InnoDB. Atribua toda a sua memória restante a este buffer. Para servidores de bancos de dados que usam somente o InnoDB como mecanismo de armazenamento e não possuem nenhum outro serviço executando (por exemplo, servidor Web), você deve atribuir até 80%% da memória disponível. Se este não for o caso, você deve avaliar cuidadosamente o consumo de memória dos outros serviços e tabelas não-InnoDB e atribuir o valor desta variável de acordo com o consumo. Tenha cuidado, pois ao atribuir valores muito altos, seu sistema começará a fazer swap (aproveitamento de espaço em disco para função de memória), o que diminuirá o desempenho significativamente. Veja também <a href="https://www.percona.com/blog/2007/11/03/choosing-innodb_buffer_pool_size/">este artigo</a>
3 weeks ago
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>
Normalmente basta configurar o {innodb_log_file_size} para 25%% do tamanho do {innodb_buffer_pool_size}. Um {innodb_log_file_size} muito grande atrasa consideravelmente o tempo de recuperação de um banco de dados após a queda do serviço. Veja também <a href="https://www.mysqlperformanceblog.com/2006/07/03/choosing-proper-innodb_log_file_size/">este artigo</a>. Você precisa desligar o servidor, remover os arquivos de log do InnoDB, configurar o novo valor em my.cnf, iniciar o servidor, e então verificar o log de erros para ver se tudo deu certo. Veja também <a href="https://mysqldatabaseadministration.blogspot.com/2007/01/increase-innodblogfilesize-proper-way.html">este post</a>
3 weeks ago
Browse all translation changes

Statistics

Percent Strings Words Chars
Total 3,351 22,218 138,715
Translated 100% 3,351 22,218 138,715
Needs editing 0% 0 0 0
Failing checks 0% 0 0 0

Last activity

Last change Aug. 31, 2020, 10:45 p.m.
Last author Maurício Meneghini Fauth

Daily activity

Daily activity

Weekly activity

Weekly activity