Translation status

21 Strings 100%
Browse Translate
583 Words 100%
3,503 Characters 100%

Strings status

Strings Words Characters
21 583 3,503
All strings Browse Translate Zen
21 583 3,503
Translated strings Browse Translate Zen

Other components

Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
loading_data 0 0 0 0 0 0 0
about_data 0 0 0 0 0 0 0
simple_sql 0 0 0 0 0 0 0
simple_sql_exercises 0 0 0 0 0 0 0
equality 0 0 0 0 0 0 0
geometries_exercises 0 0 0 0 1 0 0
spatial_relationships 0 0 0 0 0 0 0
joins 0 0 0 0 0 0 0
advanced_geometry_construction 0 0 0 0 0 0 0
index CC-BY-3.0-US 0 0 0 0 0 0 0
Browse all components

Overview

Project website postgis.net/workshops/postgis-intro
Project maintainers User avatar jef User avatar astrid_emde User avatar dmateos User avatar dkastl User avatar jsanz User avatar andischi User avatar yellow73 User avatar komzpa 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 Merge pull request #146 from AllenSH12/fixups 37f3a52
Regina Obe authored 11 days ago
Last commit in Weblate Translated using Weblate (Spanish) fc04bde
Weblate authored 5 days ago
Weblate repository https://weblate.osgeo.org/git/postgis-workshop/index/
File mask postgis-intro/sources/locale/*/LC_MESSAGES/clusterindex.po
Translation file Download postgis-intro/sources/locale/zh_Hans/LC_MESSAGES/clusterindex.po
Last change March 27, 2025, 6:47 a.m.
Last author None
2 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 21 583 3,503
Translated 100% 21 100% 583 100% 3,503
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 0% 0 0% 0 0% 0
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 24 changes 0 changes 0 changes 0 changes 0 changes
Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May

Quick numbers

583
Hosted words
21
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

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

Changes committed

  1. postgis-workshop
  2. clusterindex
  3. Chinese (Simplified)
Changes committed 2 months ago
User avatar xinbo

Translation completed

  1. postgis-workshop
  2. clusterindex
  3. Chinese (Simplified)
Translation completed 2 months ago
User avatar xinbo

Translation added

  1. postgis-workshop
  2. clusterindex
  3. Chinese (Simplified)
`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>`_：按照索引顺序重新排列表中的数据存储顺序。
2 months ago
User avatar xinbo

Translation added

  1. postgis-workshop
  2. clusterindex
  3. Chinese (Simplified)
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.
"无索引"与"有索引"的性能差异通常非常显著且易于量化，而"普通索引"与"优化索引"的差距往往需要精细测试才能辨别，且对具体工作负载高度敏感。
2 months ago
User avatar xinbo

Translation added

  1. postgis-workshop
  2. clusterindex
  3. Chinese (Simplified)
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.
理论上可行，但实际效果有限。只要索引能对数据实现「基本合理」的空间分解，查询性能的主要决定因素仍是表数据的物理存储顺序。
2 months ago
User avatar xinbo

Translation added

  1. postgis-workshop
  2. clusterindex
  3. Chinese (Simplified)
The command re-writes the ``nyc_census_blocks`` in the order defined by the spatial index ``nyc_census_blocks_geom_gist``. Can you perceive a speed difference? Maybe not, because the original data may have already had some pre-existing spatial ordering (this is not uncommon in GIS data sets).
该命令会按照空间索引``nyc_census_blocks_geom_gist``定义的顺序重写``nyc_census_blocks``表数据。您可能感知不到速度差异——因为原始数据可能已具备一定的空间预排序（这在GIS数据集中较为常见）。
2 months ago
User avatar xinbo

Translation added

  1. postgis-workshop
  2. clusterindex
  3. Chinese (Simplified)
Does Index Structure Matter?
索引结构是否影响性能？
2 months ago
User avatar xinbo

Translation added

  1. postgis-workshop
  2. clusterindex
  3. Chinese (Simplified)
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.
在现代计算机体系中，系统内存(RAM)并非最快存储层级。CPU与内存之间存在多级缓存，操作系统和处理器会以数据块为单位在缓存层级间上下迁移。若被预载入缓存的数据块恰好包含系统即将需要的数据——这将显著提升性能。通过使内存数据分布与空间结构相关联，可有效增加这种「缓存命中」的概率。
2 months ago
User avatar xinbo

Translation added

  1. postgis-workshop
  2. clusterindex
  3. Chinese (Simplified)
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.
令人惊讶的是，确实如此。将空间上「邻近」的记录在内存中也保持「邻近存储」，能显著提升相关记录共同进入服务器「内存缓存层级」的概率，从而加速内存访问效率。
2 months ago
User avatar xinbo

Translation added

  1. postgis-workshop
  2. clusterindex
  3. Chinese (Simplified)
Is clustering still necessary?
空间索引聚类是否仍有必要？
2 months ago
Browse all translation changes