postgis/performance_tips.xml — French @ OSGeo Weblate

Translation status

28	Strings		100%	Browse Translate
935	Words		100%	Browse Translate

Strings status

28	All strings — 935 words	Browse Translate Zen
28	Translated strings — 935 words	Browse Translate Zen
28	Strings waiting for review — 935 words	Browse Translate Zen

Other components

Component	Translated	Unfinished	Unfinished words	Unfinished characters	Untranslated	Checks	Suggestions	Comments
reference_raster.xml	11%	1,429	40,921	339,543	1,429	0	0	0

release_notes.xml	11%	1,597	15,436	141,542	1,597	0	0	0

reference_transformation.xml		0	0	0	0	0	0	0

reference_transaction.xml		0	0	0	0	0	0	0

faq.xml		0	0	0	0	0	0	0

postgis CC-BY-3.0		0	0	0	0	0	0	0

reference_management.xml		0	0	0	0	0	0	0

database_tuning.xml		0	0	0	0	0	0	0

faq_raster.xml		0	0	0	0	0	0	0

extras.xml		0	0	0	0	0	0	0

Browse all components

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	Have skip signature generator scan full postgis upgrade script `5e05bc3e7` Sandro Santilli authored 18 hours ago
Last commit in Weblate	Translated using Weblate (Japanese) `994b97db9` Teramoto Ikuhiro authored 3 weeks ago
Weblate repository	`https://weblate.osgeo.org/git/postgis/postgis/`
File mask	`doc/po/*/performance_tips.xml.po`
Translation file	Download `doc/po/fr/performance_tips.xml.po`
Last change	Jan. 6, 2023, 2:46 p.m.
Last author	Vincent Bre

String statistics

	Strings percent	Hosted strings	Words percent	Hosted words	Characters percent	Hosted characters
Total		28		935		6,108
Approved	0%	0	0%	0	0%	0
Waiting for review	100%	28	100%	935	100%	6,108
Translated	100%	28	100%	935	100%	6,108
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


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

Quick numbers

935

Hosted words

Hosted strings

100%

Translated

Contributors

and previous 30 days

Trends of last 30 days

—

Hosted words

—

Hosted strings

—

Translated

—

Contributors

—

None Resource update postgis / performance_tips.xml — French	The "`doc/po/fr/performance_tips.xml.po`" file was changed. 4 months ago
None String updated in the repository postgis / performance_tips.xml — 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 1 character edited Current translation Translated 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
None String updated in the repository postgis / performance_tips.xml — French	English SELECT geom_column FROM mytable WHERE bbox && ST_SetSRID('BOX3D(0 0,1 1)'::box3d,4326); French 2 characters edited Current translation Translated SELECT geom_column FROM mytable WHERE bbox &amp ;&amp ; ST_SetSRID('BOX3D(0 0,1 1)' ::box3d,4326) ; 4 months ago
None String updated in the repository postgis / performance_tips.xml — French	English Now change your query to use the && operator against bbox instead of geom_column, like: French 2 characters edited Current translation Translated Modifiez maintenant votre requête pour utiliser l'opérateur &amp ;&amp ; contre bbox au lieu de geom_column, comme suit : 4 months ago
vincentbre New translation postgis / performance_tips.xml — 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 Current translation Translated 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 : 5 months ago
vincentbre New translation postgis / performance_tips.xml — French	English and newer thread on PostGIS <ulink url="https://lists.osgeo.org/pipermail/postgis-devel/2017-June/026209.html">https://lists.osgeo.org/pipermail/postgis-devel/2017-June/026209.html</ulink> French 207 characters edited Current translation Translated et un fil d'actualités plus récent sur PostGIS <ulink url="https://lists.osgeo.org/pipermail/postgis-devel/2017-June/026209.html">https://lists.osgeo.org/pipermail/postgis-devel/2017-June/026209.html</ulink> 5 months ago
vincentbre Translation changed postgis / performance_tips.xml — French	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. French 0 characters edited Current translation Translated Maintenant émettre une requête en utilisant l'opérateur de géométrie && pour rechercher une boîte englobante qui correspond que très peu de ces lignes. Maintenant l'optimiseur de requêtes voit que la table n'a que 3 pages et 80 lignes. Il estime qu'une analyse séquentielle sur une telle petite table est beaucoup plus rapide que d'utiliser un index. Et alors il décide d'ignorer l'index GIST. Habituellement, cette estimation est correcte. Mais dans notre cas, l'opérateur && doit aller chercher chaque géométrie à partir du disque pour comparer les boîtes englobantes, et par conséquent la lecture de toutes les pages TOAST également. 5 months ago
vincentbre Translation changed postgis / performance_tips.xml — French	English The problem appears if you happen to have a table with rather large geometries, but not too many rows of them (like a table containing the boundaries of all European countries in high resolution). Then the table itself is small, but it uses lots of TOAST space. In our example case, the table itself had about 80 rows and used only 3 data pages, but the TOAST table used 8225 pages. French 0 characters edited Current translation Translated Le problème apparaît s'il vous arrive d'avoir une table avec d'assez grandes géométries, mais pas beaucoup de lignes d'entre elles (comme un tableau contenant les frontières de tous les pays européens en haute résolution). Ensuite, le tableau lui-même est petit, mais il utilise beaucoup d'espace TOAST. Dans notre exemple, le cas, la table elle-même avait environ 80 lignes et seulement 3 pages de données utilisées, mais la table TOAST 8225 pages utilisé. 5 months ago
vincentbre Translation changed postgis / performance_tips.xml — French	English Current PostgreSQL versions (including 9.6) suffer from a query optimizer weakness regarding TOAST tables. TOAST tables are a kind of "extension room" used to store large (in the sense of data size) values that do not fit into normal data pages (like long texts, images or complex geometries with lots of vertices), see <ulink url="http://www.postgresql.org/docs/current/static/storage-toast.html">the PostgreSQL Documentation for TOAST</ulink> for more information). French 0 characters edited Current translation Translated Les versions de PostgreSQL actuelles (y compris 8.0) souffrent d'une faiblesse optimiseur de requête relative les tables TOAST. Tables TOAST sont une sorte de «salle de l'extension" utilisé pour stocker de grandes valeurs (dans le sens de la taille des données) qui ne rentrent pas dans les pages de données normales (comme de longs textes, images ou des géométries complexes avec beaucoup de sommets), voir <ulink url="http://www.postgresql.org/docs/current/static/storage-toast.html"> Documentation PostgreSQL pour TOAST </ulink> pour plus d'informations). 5 months ago
vincentbre Translation changed postgis / performance_tips.xml — French	English Performance Tips French 12 characters edited Current translation Translated ~~Astuces de~~Conseils sur les performances 5 months ago

Browse all translation changes

Quick downloads

28	File in original format as translated in the repository	gettext PO file
28	All strings, converted files enriched with comments; suitable for offline translation	CSV	gettext MO	gettext PO	TBX	TMX	XLIFF 1.1 with gettext extensions	XLIFF 1.1	XLSX

Customize download

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