postgis_branch_32

performance_tips

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

	French	53%	13	483	3,395	2	14	13	0

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

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

	Japanese	71%	8	246	1,717	0	4	8	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

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

Please sign in to see the alerts.

Overview

Project website	postgis.net
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	stable-3.2
Last remote commit	Push to 3.2.6dev milestone `6e2c5206d` Regina Obe authored a week ago
Weblate repository	`https://weblate.osgeo.org/git/postgis_branch_32/postgis/`
File mask	`doc/po/*/performance_tips.xml.po`

String statistics

	Strings percent	Hosted strings	Words percent	Hosted words	Characters percent	Hosted characters
Total		252		8,415		54,972
Source		28		935		6,108
Translated	58%	147	56%	4,715	53%	29,443
Needs editing	28%	71	31%	2,669	32%	18,082
Read-only	11%	28	11%	935	11%	6,108
Failing checks	22%	57	31%	2,613	31%	17,578
Strings with suggestions	8%	22	8%	731	9%	5,128
Untranslated strings	13%	34	12%	1,031	13%	7,447

Last 12 months Previous

Activity in last 12 months


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

Quick numbers

8,415

Hosted words

252

Hosted strings

58%

Translated

1

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-05-06 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-05-06 AND state:<=needs-editing`	Add
Translated strings in a certain language	`is:translated AND language:en`	Add

None Component unlocked postgis_branch_32 / performance_tips	Fixing an alert automatically unlocked the component. 2 weeks ago
None Component locked postgis_branch_32 / performance_tips	The component was automatically locked because of an alert. 2 weeks ago
None New alert postgis_branch_32 / performance_tips	Could not update the repository. 2 weeks ago
anonymous Suggestion added postgis_branch_32 / performance_tips — French	English In case of large tables, it may be wise to divide this UPDATE into smaller portions by constraining the UPDATE to a part of the table via a WHERE clause and your primary key or another feasible criteria, and running a simple "VACUUM;" between your UPDATEs. This drastically reduces the need for temporary disk space. Additionally, if you have mixed dimension geometries, restricting the UPDATE by "WHERE dimension(geom)>2" skips re-writing of geometries that already are in 2D. French 2 characters edited En cas de grandes tables, il peut être judicieux de diviser cette mise à jour en petites portions en restreignant l'UPDATE à une partie de la table via une clause WHERE et votre clé primaire ou d'un autre critère, et exécutant un simple «VACUUM» ; entre votre mises à jour. Cela réduit considérablement le besoin d'espace disque temporaire. En outre, si vous avez des données géométriques de dimension mixte, restreindre la mise à jour en "WHERE dimension(the_geom)&gt ;2" saute la ré-écriture des géométries qui sont déjà en 2D. 4 months ago
anonymous Suggestion added postgis_branch_32 / performance_tips — French	English UPDATE mytable SET geom = ST_Force2D(geom); VACUUM FULL ANALYZE mytable; French 2 characters edited UPDATE mytable SET the_geom = ST_Force2D(the_geom) ; VACUUM FULL ANALYZE mytable ; 4 months ago
anonymous Suggestion added postgis_branch_32 / performance_tips — French	English Sometimes, you happen to have 3D or 4D data in your table, but always access it using OpenGIS compliant ST_AsText() or ST_AsBinary() functions that only output 2D geometries. They do this by internally calling the ST_Force2D() function, which introduces a significant overhead for large geometries. To avoid this overhead, it may be feasible to pre-drop those additional dimensions once and forever: French 482 characters edited Il arrive parfois que vous ayez des données 3D ou 4D dans votre table, mais que vous y accédiez toujours à l'aide des fonctions ST_AsText() ou ST_AsBinary() conformes à OpenGIS qui ne produisent que des géométries 2D. Pour ce faire, elles appellent en interne la fonction ST_Force2D(), qui introduit une surcharge importante pour les géométries de grande taille. Pour éviter cette surcharge, il peut être possible de pré-déposer ces dimensions supplémentaires une fois pour toutes : 4 months ago
anonymous Suggestion added postgis_branch_32 / performance_tips — French	English lwgeom=# ALTER TABLE my_table ALTER COLUMN geom SET not null; ALTER TABLE French 1 character edited lwgeom=# ALTER TABLE my_table ALTER COLUMN the_geom SET not null ; ALTER TABLE 4 months ago
anonymous Suggestion added postgis_branch_32 / performance_tips — French	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. French 3 characters edited 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 "the_geom" NOT NULL. 4 months ago
anonymous Suggestion added postgis_branch_32 / performance_tips — French	English SELECT geom_column FROM mytable WHERE bbox && ST_SetSRID('BOX3D(0 0,1 1)'::box3d,4326); French 4 characters edited SELECT geom_column FROM mytable WHERE bbox &amp ;&amp ; ST_SetSRID('BOX3D(0 0,1 1)' ::box3d,4326) ; 4 months ago
anonymous Suggestion added postgis_branch_32 / performance_tips — French	English SELECT AddGeometryColumn('myschema','mytable','bbox','4326','GEOMETRY','2'); UPDATE mytable SET bbox = ST_Envelope(ST_Force2D(geom)); French 2 characters edited SELECT AddGeometryColumn('myschema','mytable','bbox','4326','GEOMETRY','2') ; UPDATE mytable SET bbox = ST_Envelope(ST_Force2D(the_geom)) ; 4 months ago

Browse all component changes