Component Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
3d This language is used for source strings. This component is linked to the postgis-workshop/index repository. 0 0 0 0 0 0 0
about_data This language is used for source strings. This component is linked to the postgis-workshop/index repository. 0 0 0 0 0 0 0
advanced_geometry_construction This language is used for source strings. This component is linked to the postgis-workshop/index repository. 0 0 0 0 0 0 0
backup This language is used for source strings. This component is linked to the postgis-workshop/index repository. 0 0 0 0 0 0 0
clusterindex This language is used for source strings. This component is linked to the postgis-workshop/index repository. 0 0 0 0 1 0 0
creating_db This language is used for source strings. This component is linked to the postgis-workshop/index repository. 0 0 0 0 1 0 0
de9im This language is used for source strings. This component is linked to the postgis-workshop/index repository. 0 0 0 0 0 0 0
equality This language is used for source strings. This component is linked to the postgis-workshop/index repository. 0 0 0 0 0 0 0
geography This language is used for source strings. This component is linked to the postgis-workshop/index repository. 0 0 0 0 0 0 0
geography_exercises This language is used for source strings. This component is linked to the postgis-workshop/index repository. 0 0 0 0 0 0 0
geometries This language is used for source strings. This component is linked to the postgis-workshop/index repository. 0 0 0 0 0 0 0
geometries_exercises This language is used for source strings. This component is linked to the postgis-workshop/index repository. 0 0 0 0 1 0 0
geometry_returning This language is used for source strings. This component is linked to the postgis-workshop/index repository. 0 0 0 0 0 0 0
geometry_returning_exercises This language is used for source strings. This component is linked to the postgis-workshop/index repository. 0 0 0 0 1 0 0
Glossary glossary 1 This language is used for source strings. This component is linked to the postgis-workshop/index repository. CC-BY-3.0-US 0 0 0 0 0 0 0
history_tracking This language is used for source strings. This component is linked to the postgis-workshop/index repository. 0 0 0 0 0 0 0
index This language is used for source strings. CC-BY-3.0-US 0 0 0 0 0 0 0
indexing This language is used for source strings. This component is linked to the postgis-workshop/index repository. 0 0 0 0 14 0 0
installation This language is used for source strings. This component is linked to the postgis-workshop/index repository. CC-BY-3.0-US 0 0 0 0 0 0 0
introduction This language is used for source strings. This component is linked to the postgis-workshop/index repository. 0 0 0 0 21 0 0
joins This language is used for source strings. This component is linked to the postgis-workshop/index repository. 0 0 0 0 0 0 0
joins_advanced This language is used for source strings. This component is linked to the postgis-workshop/index repository. 0 0 0 0 0 0 0
joins_exercises This language is used for source strings. This component is linked to the postgis-workshop/index repository. 0 0 0 0 0 0 0
knn This language is used for source strings. This component is linked to the postgis-workshop/index repository. 0 0 0 0 0 0 0
license This language is used for source strings. This component is linked to the postgis-workshop/index repository. 0 0 0 0 0 0 0
linear_referencing This language is used for source strings. This component is linked to the postgis-workshop/index repository. 0 0 0 0 0 0 0
loading_data This language is used for source strings. This component is linked to the postgis-workshop/index repository. 0 0 0 0 1 0 0
postgis-functions This language is used for source strings. This component is linked to the postgis-workshop/index repository. 0 0 0 0 0 0 0
projection This language is used for source strings. This component is linked to the postgis-workshop/index repository. 0 0 0 0 0 0 0
projection_exercises This language is used for source strings. This component is linked to the postgis-workshop/index repository. 0 0 0 0 0 0 0
schemas This language is used for source strings. This component is linked to the postgis-workshop/index repository. 0 0 0 0 0 0 0
security This language is used for source strings. This component is linked to the postgis-workshop/index repository. 0 0 0 0 1 0 0
simple_sql This language is used for source strings. This component is linked to the postgis-workshop/index repository. 0 0 0 0 0 0 0
simple_sql_exercises This language is used for source strings. This component is linked to the postgis-workshop/index repository. 0 0 0 0 0 0 0
spatial_relationships This language is used for source strings. This component is linked to the postgis-workshop/index repository. 0 0 0 0 0 0 0
spatial_relationships_exercises This language is used for source strings. This component is linked to the postgis-workshop/index repository. 0 0 0 0 0 0 0
tuning This language is used for source strings. This component is linked to the postgis-workshop/index repository. 0 0 0 0 0 0 0
upgrades This language is used for source strings. This component is linked to the postgis-workshop/index repository. 0 0 0 0 0 0 0
validity This language is used for source strings. This component is linked to the postgis-workshop/index repository. 0 0 0 0 0 0 0
welcome This language is used for source strings. This component is linked to the postgis-workshop/index repository. 0 0 0 0 0 0 0

Overview

Project website postgis.net/workshops/postgis-intro
Project maintainers User avatar cvvergara User avatar andischi User avatar dkastl User avatar yellow73 User avatar komzpa User avatar strk User avatar dmateos User avatar robe User avatar darkblueb User avatar jsanz User avatar astrid_emde User avatar jef
Translation license CC-BY-3.0-US installation glossary 1 index

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 1,732 30,167 202,745
Translated 100% 1,732 100% 30,167 100% 202,745
Needs editing 0% 0 0% 0 0% 0
Read-only 99% 1,730 99% 30,163 99% 202,721
Failing checks 2% 41 2% 852 2% 5,327
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 43 changes 0 changes 0 changes 0 changes 1 change 0 changes 12 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 40 changes 0 changes
Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov

Quick numbers

30,167
Hosted words
1,732
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
—
—
Hosted strings
—
—
Translated
—
—
Contributors
—
User avatar None

Resource update

postgis-workshop / validity — English

The "postgis-intro/sources/locale/pot/validity.pot" file was changed. 7 months ago
User avatar None

Resource update

postgis-workshop / clusterindex — English

The "postgis-intro/sources/locale/pot/clusterindex.pot" file was changed. 7 months ago
User avatar None

String updated in the repository

postgis-workshop / clusterindex — English

`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>`_: Re-orders the data in a table to match the ordering in the index.
7 months ago
User avatar None

String updated in the repository

postgis-workshop / clusterindex — English

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.
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.
7 months ago
User avatar None

String updated in the repository

postgis-workshop / clusterindex — English

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.
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.
7 months ago
User avatar None

String updated in the repository

postgis-workshop / clusterindex — English

Does Index Structure Matter?
Does Index Structure Matter?
7 months ago
User avatar None

String updated in the repository

postgis-workshop / clusterindex — English

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.
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.
7 months ago
User avatar None

String updated in the repository

postgis-workshop / clusterindex — English

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.
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.
7 months ago
User avatar None

String updated in the repository

postgis-workshop / clusterindex — English

Is clustering still necessary?
Is clustering still necessary?
7 months ago
User avatar None

String updated in the repository

postgis-workshop / clusterindex — English

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.
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.
7 months ago
Browse all language changes