Translation status

46 Strings 100%
Browse Translate
1,098 Words 100%
7,106 Characters 100%

Strings status

Strings Words Characters
46 1,098 7,106
All strings Browse Translate Zen
46 1,098 7,106
Translated strings Browse Translate Zen
8 10 132
Strings with any failing checks Browse Translate Zen
8 10 132
Translated strings with any failing checks Browse Translate Zen
8 10 132
Failing check: Unchanged translation Browse Translate Zen

Other components

Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
geometry_returning 0 0 0 0 0 0 0
projection_exercises 0 0 0 0 1 0 0
backup 0 0 0 0 2 0 0
license 0 0 0 0 0 0 0
installation CC-BY-3.0-US 0 0 0 0 0 0 0
equality 0 0 0 0 0 0 0
topology CC-BY-3.0-US 0 0 0 0 4 0 0
geography_exercises 0 0 0 0 0 0 0
security 0 0 0 0 0 0 0
clusterindex 0 0 0 0 0 0 0
Browse all components

Overview

Project website postgis.net/workshops/postgis-intro
Project maintainers User avatar yellow73 User avatar jef User avatar astrid_emde User avatar dmateos User avatar dkastl User avatar jsanz User avatar cvvergara User avatar andischi User avatar komzpa
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 Merge pull request #155 from osgeoweblate/weblate-postgis-workshop-index 1cb0b08
Regina Obe authored 4 days ago
Last commit in Weblate Translated using Weblate (Spanish) 60356e8
Weblate authored 4 days ago
Weblate repository https://weblate.osgeo.org/git/postgis-workshop/index/
File mask postgis-intro/sources/locale/*/LC_MESSAGES/tuning.po
Translation file Download postgis-intro/sources/locale/es/LC_MESSAGES/tuning.po
Last change Sept. 26, 2025, 7:20 a.m.
Last author None
4 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 46 1,098 7,106
Translated 100% 46 100% 1,098 100% 7,106
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 17% 8 1% 10 1% 132
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 10 changes 0 changes 0 changes 0 changes 50 changes
Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug

Quick numbers

1,098
Hosted words
46
Hosted strings
100%
Translated
3
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
+86%
Translated
+13%
+100%
Contributors
—
User avatar robe

Changes committed

  1. postgis-workshop
  2. tuning
  3. Spanish
Changes committed 4 days 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.
4 days ago
User avatar None

Changes committed

  1. postgis-workshop
  2. tuning
  3. Spanish
Changes committed 3 weeks 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.
3 weeks ago
User avatar None

Changes committed

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

Translation completed

  1. postgis-workshop
  2. tuning
  3. Spanish
Translation completed a month ago
User avatar paulo

Translation added

  1. postgis-workshop
  2. tuning
  3. Spanish
Back in pgAdmin, click the server again select *Disconnect*.
De vuelta en pgAdmin, haz clic nuevamente en el servidor y selecciona *Disconnect*.
a month ago
User avatar paulo

Translation added

  1. postgis-workshop
  2. tuning
  3. Spanish
In Windows Services (``services.msc``) right-click **PostgreSQL** and select *Restart*.
En Servicios de Windows (services.msc), haz clic derecho en **PostgreSQL** y selecciona *Restart*.
a month ago
User avatar paulo

Translation added

  1. postgis-workshop
  2. tuning
  3. Spanish
In pgAdmin, right-click the server **PostGIS (localhost:5432)** and select *Disconnect*.
En pgAdmin, haz clic derecho en el servidor **PostGIS (localhost:5432)** y selecciona *Disconnect*.
a month ago
User avatar paulo

Translation added

  1. postgis-workshop
  2. tuning
  3. Spanish
After these changes are made, save changes and reload the configuration. The easiest way to do this is to restart the PostgreSQL service.
Después de realizar estos cambios, guarda y recarga la configuración. La forma más sencilla de hacerlo es reiniciando el servicio de PostgreSQL.
a month ago
Browse all translation changes