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
1 1 14
Strings with suggestions Browse Translate Zen
5 5 72
Strings with any failing checks Browse Translate Zen
5 5 72
Translated strings with any failing checks Browse Translate Zen
1 1 16
Translated strings with dismissed checks Browse Translate Zen
5 5 72
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 1 0 0
projection_exercises 0 0 0 0 8 0 0
simple_sql_exercises 0 0 0 0 13 0 0
index CC-BY-3.0-US 0 0 0 0 0 0 0
backup 0 0 0 0 4 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
joins_advanced 0 0 0 0 0 0 0
topology CC-BY-3.0-US 0 0 0 0 0 1 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) a17ba65
Weblate authored 5 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/sv/LC_MESSAGES/tuning.po
Last change June 6, 2025, 6:30 a.m.
Last author None
2 weeks 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 10% 5 1% 5 1% 72
Strings with suggestions 2% 1 1% 1 1% 14
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 0 changes 0 changes 0 changes 0 changes 0 changes
Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May

Quick numbers

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

Trends of last 30 days

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

Changes committed

  1. postgis-workshop
  2. tuning
  3. Swedish
Changes committed 2 weeks ago
User avatar yeager

Translation changed

  1. postgis-workshop
  2. tuning
  3. Swedish
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.
Förutom det minne som PostgreSQL avsätter för `` delade shared_buffertar s`` tar frågeplaneraren också hänsyn till hur många diskblock operativsystemet kan ha cachat som en del av dess virtuella filsystem. För system med stor mängd minne kan detta vara ganska stort. Den "``effektiva ctive_cachestorleken"_size`` är ungefär lika stor som maskinens minne, minus de "delade buffertarna", minus "arbetsminnet"``shared_buffers``, minus ``work_mem`` gånger det förväntade antalet anslutningar, minus det minne som krävs för andra processer som körs på maskinen, minus ca 1 GB för andra slumpmässiga behov hos operativsystemet. Databasen kommer inte att **använda** den extra cachen direkt, men den kommer att beräkna planer som förväntar sig att operativsystemet har cachat filsystemdata i ungefär lika mycket minne.
2 weeks ago
User avatar None

Changes committed

  1. postgis-workshop
  2. tuning
  3. Swedish
Changes committed 2 weeks ago
User avatar yeager

Translation changed

  1. postgis-workshop
  2. tuning
  3. Swedish
random_page_cost
slumpmässig_sidkostnadrandom_page_cost
2 weeks ago
User avatar yeager

Translation changed

  1. postgis-workshop
  2. tuning
  3. Swedish
Basic PostgreSQL Tuning
Grundläggande PostgreSQL-tunjustering
2 weeks ago
User avatar None

Changes committed

  1. postgis-workshop
  2. tuning
  3. Swedish
Changes committed 2 weeks ago
User avatar yeager

Translation uploaded

  1. postgis-workshop
  2. tuning
  3. Swedish
Back in pgAdmin, click the server again select *Disconnect*.
Tillbaka i pgAdmin klickar du på servern igen och väljer *Disconnect*.
2 weeks ago
User avatar yeager

Translation uploaded

  1. postgis-workshop
  2. tuning
  3. Swedish
In Windows Services (``services.msc``) right-click **PostgreSQL** and select *Restart*.
I Windows Services (``services.msc``) högerklickar du på **PostgreSQL** och väljer *Restart*.
2 weeks ago
User avatar yeager

Translation uploaded

  1. postgis-workshop
  2. tuning
  3. Swedish
In pgAdmin, right-click the server **PostGIS (localhost:5432)** and select *Disconnect*.
I pgAdmin högerklickar du på servern **PostGIS (localhost:5432)** och väljer *Disconnect*.
2 weeks ago
User avatar yeager

Translation uploaded

  1. postgis-workshop
  2. tuning
  3. Swedish
After these changes are made, save changes and reload the configuration. The easiest way to do this is to restart the PostgreSQL service.
När dessa ändringar har gjorts sparar du ändringarna och laddar om konfigurationen. Det enklaste sättet att göra detta är att starta om PostgreSQL-tjänsten.
2 weeks ago
Browse all translation changes