postgis/performance_tips.xml @ OSGeo Weblate

Language	Translated	Unfinished	Unfinished words	Unfinished characters	Untranslated	Checks	Suggestions	Comments
English		0	0	0	0	10	0	0

French		0	0	0	0	0	0	0

German	71%	8	246	1,717	0	4	0	0

Italian	53%	13	483	3,395	1	7	0	0

Japanese		0	0	0	0	0	0	0

Korean	60%	11	412	2,901	1	2	0	0

Polish	0%	28	935	6,108	28	0	0	0

Portuguese (Brazil)	60%	11	412	2,901	1	2	0	0

Russian	0%	28	935	6,108	28	0	1	0

Spanish	53%	13	483	3,395	1	6	0	0

Please sign in to see the alerts.

Overview

Project website	postgis.net
Project maintainers	komzpa cvvergara strk robe
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://git.osgeo.org/gitea/postgis/postgis.git`
Repository branch	master
Last remote commit	Show obtained output on failure, in oriented_envelope test `36fcdd626` Sandro Santilli authored yesterday
Last commit in Weblate	Translated using Weblate (Japanese) `994b97db9` Teramoto Ikuhiro authored 2 weeks ago
Weblate repository	`https://weblate.osgeo.org/git/postgis/postgis/`
File mask	`doc/po/*/performance_tips.xml.po`

String statistics

	Strings percent	Hosted strings	Words percent	Hosted words	Characters percent	Hosted characters
Total		280		9,350		61,080
Source		28		935		6,108
Approved	0%	0	0%	0	0%	0
Waiting for review	50%	140	48%	4,509	46%	28,447
Translated	60%	168	58%	5,444	56%	34,555
Needs editing	18%	52	21%	2,008	22%	13,557
Read-only	10%	28	10%	935	10%	6,108
Failing checks	11%	31	19%	1,791	19%	11,909
Strings with suggestions	1%	1	1%	2	1%	16
Untranslated strings	21%	60	20%	1,898	21%	12,968

Last 12 months Previous

Activity in last 12 months


May	Jun	Jul	Aug	Sep	Oct	Nov	Dec	Jan	Feb	Mar	Apr

Quick numbers

9,350

Hosted words

280

Hosted strings

60%

Translated

Contributors

and previous 30 days

Trends of last 30 days

—

Hosted words

—

Hosted strings

—

Translated

—

+100%

Contributors

—

Search

Advanced query builder

Query examples

Review strings changed by other users	`changed:>=2023-04-29 AND NOT changed_by:anonymous`	Add
Translated strings	`state:>=translated`	Add
Strings with comments	`has:comment`	Add
Strings with any failing checks	`has:check`	Add
Strings with suggestions from others	`has:suggestion AND NOT suggestion_author:anonymous`	Add
Approved strings with suggestions	`state:approved AND has:suggestion`	Add
All untranslated strings added the past month	`added:>=2023-04-29 AND state:<=needs-editing`	Add
Translated strings in a certain language	`is:translated AND language:en`	Add

None Component unlocked postgis / performance_tips.xml	Fixing an alert automatically unlocked the component. 12 days ago
None Component locked postgis / performance_tips.xml	The component was automatically locked because of an alert. 13 days ago
None New alert postgis / performance_tips.xml	Could not update the repository. 13 days ago
yellow73 Translation changed postgis / performance_tips.xml — Japanese	English lwgeom=# CLUSTER my_geom_index ON my_table; ERROR: cannot cluster when index access method does not handle null values HINT: You may be able to work around this by marking column "geom" NOT NULL. Japanese 1 character edited Current translation Translated lwgeom=# CLUSTER my_geom_index ON my_table; ERROR: cannot cluster when index access method does not handle null values (エラー: インデックスアクセスメソッドがNULL値を扱わない場合クラスタ化できません) HINT: You may be able to work around this by marking column "geom" NOT NULL. (ヒント: 列"the_geom"をNOT NULLとすることで、これを回避できるかもしれません) 2 weeks ago
yellow73 Translation changed postgis / performance_tips.xml — Japanese	English However, currently PostgreSQL does not allow clustering on PostGIS GIST indices because GIST indices simply ignores NULL values, you get an error message like: Japanese 2 characters edited Current translation Translated しかし、GiSTインデックスは単純にNULL値を無視するため現在のところPostGISのGiSTインデックスのクラスタリングはできず、次のようなエラーメッセージを得ます。 2 weeks ago
yellow73 Translation changed postgis / performance_tips.xml — Japanese	English For tables that are mostly read-only, and where a single index is used for the majority of queries, PostgreSQL offers the CLUSTER command. This command physically reorders all the data rows in the same order as the index criteria, yielding two performance advantages: First, for index range scans, the number of seeks on the data table is drastically reduced. Second, if your working set concentrates to some small intervals on the indices, you have a more efficient caching because the data rows are spread along fewer data pages. (Feel invited to read the CLUSTER command documentation from the PostgreSQL manual at this point.) Japanese 2 characters edited Current translation Translated 読み込むことがほとんどで、かつほとんどのクエリでひとつのインデックスを使うようなテーブルのために、PostgreSQLはCLUSTERコマンドを提供しています。このコマンドは、全てのデータ行を、インデックス基準にあわせて物理的に再整理するので、二つの性能の利点を生みます。一つは、インデックスの範囲走査のために、データテーブルのシーク回数が劇的に減少することです。もう一つは、いくつかの小さなインデックス間隔に集中する場合には、データ行が分布するデータページがより少なくなることで、より効率的なキャッシュを持つことです (この点は、PostgreSQLマニュアルのCLUSTERコマンドのドキュメントを読むように仕向けられていると感じて下さい)。 2 weeks ago
yellow73 Translation changed postgis / performance_tips.xml — Japanese	English CLUSTERing on geometry indices Japanese 1 character edited Current translation Translated ジオメトリインデックスでCLUSTERを実行する 2 weeks ago
yellow73 Translation changed postgis / performance_tips.xml — Japanese	English The first workaround is to force the query planner to use the index. Send "SET enable_seqscan TO off;" to the server before issuing the query. This basically forces the query planner to avoid sequential scans whenever possible. So it uses the GIST index as usual. But this flag has to be set on every connection, and it causes the query planner to make misestimations in other cases, so you should "SET enable_seqscan TO on;" after the query. Japanese 2 characters edited Current translation Translated 一つは、クエリプランナにインデックスの使用を強制することです。クエリを発行する前に"SET enable_seqscan TO off;"をサーバに送信します。これは基本的にクエリプランナに対して可能な限り順に走査することを避けるよう強制します。そのためGiSTインデックスを通常使うようになります。しかし、このフラグは接続するたびに設定しなければならず、他のケースにおいてはクエリプランナに誤った見積もりをさせることになるので、 "SET enable_seqscan TO on;"をクエリの後に送信すべきです。 2 weeks ago
yellow73 Translation changed postgis / performance_tips.xml — Japanese	English Now issue a query where you use the geometry operator && to search for a bounding box that matches only very few of those rows. Now the query optimizer sees that the table has only 3 pages and 80 rows. It estimates that a sequential scan on such a small table is much faster than using an index. And so it decides to ignore the GIST index. Usually, this estimation is correct. But in our case, the && operator has to fetch every geometry from disk to compare the bounding boxes, thus reading all TOAST pages, too. Japanese 2 characters edited Current translation Translated ここで、ジオメトリ演算子の&&を使って、ほとんどマッチしないようなバウンダリボックスを検索するクエリを出してみます。クエリオプティマイザにはテーブルは3ページ80行しかないように見えます。オプティマイザは、小さなテーブルを順に走査する方がインデックスを使うよりも早いと見積もります。そして、GiSTインデックスは無視すると決めます。通常なら、この見積もりは正しいです。しかし、この場合は&&演算子が全てのジオメトリをディスクから呼び出してバウンディングボックスと比較しなければならなくなり、ゆえに、全てのTOASTページもまた呼び出す必要があります。 2 weeks ago
anonymous Suggestion added postgis / performance_tips.xml — Russian	English Performance Tips Russian 38 characters edited Советы по повышению производительности 2 weeks ago

Browse all component changes