Language Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
English 0 0 0 0 1 0 0
Chinese (Simplified) 4% 20 581 3,490 20 0 0 0
German 0% 21 583 3,503 21 0 0 0
Italian 0% 21 583 3,503 21 0 0 0
Japanese 0 0 0 0 0 0 0
Spanish 85% 3 101 552 3 0 0 0
Please sign in to see the alerts.

Overview

Project website postgis.net/workshops/postgis-intro
Project maintainers User avatar komzpa User avatar yellow73 User avatar dmateos User avatar dkastl User avatar astrid_emde User avatar jsanz User avatar andischi User avatar cvvergara User avatar jef
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 #126 from enockseth/fix-typo 9925f56
Paul Ramsey authored yesterday
Last commit in Weblate Translated using Weblate (Japanese) d028968
Teramoto Ikuhiro authored a month ago
Weblate repository https://weblate.osgeo.org/git/postgis-workshop/index/
File mask postgis-intro/sources/locale/*/LC_MESSAGES/clusterindex.po
3 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 126 3,498 21,018
Source 21 583 3,503
Translated 48% 61 47% 1,650 47% 9,970
Needs editing 0% 0 0% 0 0% 0
Read-only 16% 21 16% 583 16% 3,503
Failing checks 1% 1 2% 83 2% 466
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 51% 65 52% 1,848 52% 11,048
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 1 change 0 changes 0 changes 6 changes 0 changes 8 changes 0 changes 0 changes 0 changes 3 changes 0 changes 43 changes 0 changes 0 changes 0 changes 8 changes 22 changes
Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun

Quick numbers

3,498
Hosted words
126
Hosted strings
48%
Translated
1
Contributors
and previous 30 days

Trends of last 30 days

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

Changes committed

  1. postgis-workshop
  2. clusterindex
  3. Spanish
Changes committed a month ago
User avatar dmateos

Translation added

  1. postgis-workshop
  2. clusterindex
  3. Spanish
`CLUSTER <https://www.postgresql.org/docs/current/sql-cluster.html>`_: Re-orders the data in a table to match the ordering in the index.
`CLUSTER <https://www.postgresql.org/docs/current/sql-cluster.html>`_: Reordena los datos en la tabla para que coincida con el orden del índice.
a month ago
User avatar dmateos

Translation added

  1. postgis-workshop
  2. clusterindex
  3. Spanish
Function List
Lista de funciones
a month ago
User avatar dmateos

Translation added

  1. postgis-workshop
  2. clusterindex
  3. Spanish
The difference between "no index" and "index" is generally huge and highly measurable. The difference between "mediocre index" and "great index" usually takes quite careful measurement to discern, and can be very sensitive to the workload being tested.
La diferencia entre "sin indice" e "índice" normalmente es muy grande y muy medible. La diferencia entre "índice mediocre" y "gran índice" normalmente requiere una medida muy cuidadosa para diferenciar y puede ser muy sensible a la carga de trabajo que se esté testando.
a month ago
User avatar dmateos

Translation added

  1. postgis-workshop
  2. clusterindex
  3. Spanish
In theory, yes. In practice, no really. As long as the index is a "pretty good" spatial decomposition of the data, the main determinant of performance will be the order of the actual table tuples.
En teoría, sí. En la práctica, realmente no. Ya que el índice es una descomposición espacial de los datos "bastante buena", el principal factor que afectará al rendimiento será el orden de las tuplas de la tabla.
a month ago
User avatar dmateos

Translation added

  1. postgis-workshop
  2. clusterindex
  3. Spanish
Does Index Structure Matter?
¿Importa la Estructura del Índice?
a month ago
User avatar dmateos

Translation added

  1. postgis-workshop
  2. clusterindex
  3. Spanish
System RAM is not the fastest memory on a modern computer. There are several levels of cache between system RAM and the actual CPU, and the underlying operating system and processor will move data up and down the cache heirarchy in blocks. If the block getting moved up happens to include the piece of data the system will need next... that's a big win. Correlating the memory structure with the spatial structure is a way in increase the odds of that win happening.
La RAM del sistema no es la memoria más rápida en un ordenador moderno. Hay muchos niveles de caché entre el sistema RAM y la CPU, y el sistema operativo y el procesador moverán datos arriba y abajo en esa jerarquia de caché en bloques. Si resulta que el bloque que se está moviendo incluye el trozo de datos que el sistema necesitará justo después,... es una gran victoria. Correlar la estructura de la memoria con la estructura espacial es un forma de aumentar las posibilidades de que esto suceda.
a month ago
User avatar dmateos

Translation added

  1. postgis-workshop
  2. clusterindex
  3. Spanish
Surprisingly, yes. Keeping records that are "near each other" in space "near each other" in memory increases the odds that related records will move up the servers "memory cache heirarchy" together, and thus make memory accesses faster.
Sorprendentemente, sí. Mantener registros que están "cerca del otro" en espacios "cerca del otro" en la memoria aumenta las posibilidades de que registros relacionados se muevan en la "jerarquia de memoria caché" juntos haciendo el acceso a la memoria más rápido.
a month ago
User avatar dmateos

Translation added

  1. postgis-workshop
  2. clusterindex
  3. Spanish
Is clustering still necessary?
¿Es todavía necesario el clustering?
a month ago
User avatar dmateos

Translation added

  1. postgis-workshop
  2. clusterindex
  3. Spanish
Most modern databases are run using SSD storage, which is much faster at random access than old spinning magnetic media. Also, most modern databases are running on top of data which is small enough to fit into the RAM of the database server, and ends up there as the operating system "virtual filesystem" caches it.
La mayoría de las bases de datos modernas funcionan sobre almacenamiento SSD, que es mucho más rápido para accesos aleatorios que los viejos medios discos magnéticos girantes. Además, la mayoría de las bases de datos modernas funcionan sobre datos que son los bastante pequeños para caber en la RAM del servidor de la base de datos, y terminan allí según el "sistema de archivos virtual" del sistema operativo los va cacheando.
a month ago
Browse all component changes