Language Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
English 0 0 0 0 7 0 0
German 0% 46 1,098 7,106 46 0 1 0
Italian 0% 46 1,098 7,106 46 0 1 0
Japanese 0 0 0 0 0 0 0
Spanish 0 0 0 0 7 0 0
Swedish 0 0 0 0 5 1 0
Please sign in to see the alerts.

Overview

Project website postgis.net/workshops/postgis-intro
Project maintainers User avatar jef User avatar komzpa User avatar astrid_emde User avatar yellow73 User avatar dmateos User avatar dkastl User avatar jsanz User avatar andischi User avatar cvvergara
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository https://github.com/postgis/postgis-workshops.git
Repository branch master
Last remote commit Update sql cheat sheet with makevalid example 5f99414
Paul Ramsey authored 13 days ago
Last commit in Weblate Translated using Weblate (Spanish) 61fed39
juan sebastian jimenez aldana authored 2 weeks ago
Weblate repository https://weblate.osgeo.org/git/postgis-workshop/index/
File mask postgis-intro/sources/locale/*/LC_MESSAGES/tuning.po
2 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 276 6,588 42,636
Source 46 1,098 7,106
Translated 66% 184 66% 4,392 66% 28,424
Needs editing 0% 0 0% 0 0% 0
Read-only 16% 46 16% 1,098 16% 7,106
Failing checks 6% 19 1% 19 1% 286
Strings with suggestions 1% 3 1% 3 1% 42
Untranslated strings 33% 92 33% 2,196 33% 14,212
Last 12 months Previous

Activity in last 12 months

1 change 1 change 0 changes 1 change 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 112 changes 0 changes 0 changes 0 changes 50 changes 0 changes 4 changes 0 changes 4 changes
Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct

Quick numbers

6,588
Hosted words
276
Hosted strings
66%
Translated
2
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+66%
—
Contributors
+100%
User avatar None

Changes committed

  1. postgis-workshop
  2. tuning
  3. Spanish
Changes committed 2 weeks ago
User avatar jusjimeneza

Translation changed

  1. postgis-workshop
  2. tuning
  3. Spanish
*Recommended value*: 32MB
*Valor Recommended valueado*: 32MB
2 weeks ago
User avatar jusjimeneza

Translation changed

  1. postgis-workshop
  2. tuning
  3. Spanish
PostgreSQL is a very versatile database system, capable of running efficiently in very low-resource environments and environments shared with a variety of other applications. In order to ensure it will run properly for many different environments, the default configuration is very conservative and not terribly appropriate for a high-performance production database. Add the fact that geospatial databases have different usage patterns, and the data tend to consist of fewer, much larger records than non-geospatial databases, and you can see that the default configuration will not be totally appropriate for our purposes.
PostgreSQL es un sistema de bases de datos muy versátil, capaz de ejecutarsefuncionar de manera eficiente en entornos decon muy bajpocos recursos y en entornos compartidos con una variedad de otras aplicaciones. Para garantizar que funcione correctsu correcto funcionamienteo en muchos entornos diferentes, la configuración predeterminada es muy conservadora y no resulta del todomuy adecuada para una base de datos de producción de alto rendimiento. Si añadimos el hecho d esto le sumamos que las bases de datos geoespaciales tienen diferentes patrones de uso, y diferentes y que los datos tienden asuelen consistir en menos registros menos numerosos, pero mucho más grandes que enlos de las bases de datos no geoespaciales, se puede veres evidente que la configuración por defecto no seráredeterminada no es totalmente apropidecuada para nuestros propósitofines.
2 weeks ago
User avatar jusjimeneza

Contributor joined

  1. postgis-workshop
  2. tuning
  3. Spanish
Contributor joined 2 weeks ago
User avatar robe

Changes committed

  1. postgis-workshop
  2. tuning
  3. Spanish
Changes committed a month ago
User avatar robe

Translation changed

  1. postgis-workshop
  2. tuning
  3. Spanish
In addition to the memory PostgreSQL sets aside for ``shared_buffers`` the query planner also takes into account how many disk blocks the operating system may have cached as part of its virtual file system. For systems with large amount of memory, this can be quite large. The ``effective_cache_size`` is approximately the amount of memory on the machine, less the ``shared_buffers``, less the ``work_mem`` times the expected number of connections, less any memory required for any other processes running on the machine, less about 1GB for other random operating system needs. The database will not **use** the extra cache directly, but it will compute plans expecting that the operating system has cached filesystem data in about that much memory.
Además de la memoria que PostgreSQL reserva para ``shared_buffers``, el planificador de consultas también tiene en cuenta cuántos bloques de disco puede haber almacenado en caché el sistema operativo como parte de su sistema de archivos virtual. En sistemas con grandes cantidades de memoria, esto puede ser bastante elevado. El ``effective_cache_size`` es aproximadamente la cantidad de memoria de la máquina, menos ``shared_buffers``, menos ``work_mem`` multiplicado por el número esperado de conexiones, menos cualquier memoria requerida para otros procesos que se estén ejecutando en la máquina, menos alrededor de 1GB para otras necesidades aleatorias del sistema operativo. La base de datos no usará directamente esta memoria adicional como caché, pero calculará planes suponiendo que el sistema operativo ha almacenado en caché datos del sistema de archivos en aproximadamente esa cantidad de memoria.
a month ago
User avatar None

Changes committed

  1. postgis-workshop
  2. tuning
  3. Spanish
Changes committed 2 months ago
User avatar paulo

Translation changed

  1. postgis-workshop
  2. tuning
  3. Spanish
As such you must consider how many connections and the complexity of expected queries before increasing this value. The **benefit** to increasing is that the processing of more of these operations, including ORDER BY, and DISTINCT clauses, merge and hash joins, hash-based aggregation and hash-based processing of subqueries, can be accomplished without incurring disk writes. The **cost** of increasing is memory that will be used **per connection**, which can be quite high with production levels of connections.
Por lo tanto, debes considerar cuántas conexiones habrá y la complejidad de las consultas esperadas antes de aumentar este valor. El
 **beneficio** de aumentarlo es el procesamiento de más operaciones —incluyendo cláusulas ORDER BY y DISTINCT, uniones merge y hash, agregaciones basadas en hash y procesamiento de subconsultas con hash— puede realizarse sin incurrir en escrituras a disco. El **costo** de aumentarlo es que la memoria que se usará por conexión, lo que puede ser bastante elevado en niveles de producción con muchas conexiones.
2 months ago
User avatar None

Changes committed

  1. postgis-workshop
  2. tuning
  3. Spanish
Changes committed 2 months ago
User avatar paulo

Translation completed

  1. postgis-workshop
  2. tuning
  3. Spanish
Translation completed 2 months ago
Browse all component changes