postgis_branch_32/using_postgis_dataman

Translation status

500	Strings		16%	Browse Translate
10,824	Words		5%	Browse Translate

Strings status

500	All strings — 10,824 words	Browse Translate Zen
82	Translated strings — 593 words	Browse Translate Zen
418	Unfinished strings — 10,231 words	Browse Translate Zen
418	Untranslated strings — 10,231 words	Browse Translate Zen
400	Strings with suggestions — 9,498 words	Browse Translate Zen
18	Unfinished strings without suggestions — 733 words	Browse Translate Zen
14	Strings with any failing checks — 134 words	Browse Translate Zen
14	Translated strings with any failing checks — 134 words	Browse Translate Zen
8	Failing check: Unchanged translation — 21 words	Browse Translate Zen
6	Failing check: Punctuation spacing — 113 words	Browse Translate Zen

Other components

Component	Translated	Unfinished	Unfinished words	Unfinished characters	Untranslated	Checks	Suggestions	Comments
extras	0%	3	45	318	3	0	3	0

reference_troubleshooting	0%	26	407	3,121	26	2	26	0

reference_bbox	0%	117	1,991	19,058	117	3	116	0

reference_overlay	0%	143	2,782	24,240	143	2	8	0

reference_version	0%	88	709	8,318	88	1	88	0

database_tuning	0%	33	543	3,893	33	0	33	0

reference_cluster	0%	55	1,131	9,962	55	1	47	0

using_postgis_query	0%	109	2,146	16,760	109	0	92	0

reference_relationship	0%	273	5,065	46,644	273	2	213	0

reference_srs	0%	54	978	8,949	54	3	50	0

Browse all components

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 21 hours ago
Weblate repository	`https://weblate.osgeo.org/git/postgis_branch_32/postgis/`
File mask	`doc/po/*/using_postgis_dataman.xml.po`
Translation file	Download `doc/po/fr/using_postgis_dataman.xml.po`
Last change	None
Last author	None

String statistics

	Strings percent	Hosted strings	Words percent	Hosted words	Characters percent	Hosted characters
Total		500		10,824		75,744
Translated	16%	82	5%	593	5%	4,495
Needs editing	0%	0	0%	0	0%	0
Read-only	0%	0	0%	0	0%	0
Failing checks	2%	14	1%	134	1%	1,214
Strings with suggestions	80%	400	87%	9,498	86%	65,555
Untranslated strings	83%	418	94%	10,231	94%	71,249

Last 12 months Previous

Activity in last 12 months


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

Quick numbers

10,824

Hosted words

500

Hosted strings

16%

Translated

Contributors

and previous 30 days

Trends of last 30 days

—

Hosted words

—

Hosted strings

—

Translated

—

+100%

Contributors

—

anonymous Suggestion added postgis_branch_32 / using_postgis_dataman — French	English For more information see the Postgres manual section on <ulink url="https://www.postgresql.org/docs/current/runtime-config-query.html">Query Planning</ulink>. French 167 characters edited Pour plus d'informations, voir la section du manuel Postgres sur <ulink url="https://www.postgresql.org/docs/current/runtime-config-query.html">Query Planning</ulink>. 2 weeks ago
anonymous Suggestion added postgis_branch_32 / using_postgis_dataman — French	English If <command>SET ENABLE_SEQSCAN TO OFF;</command> does not help your query, the query may be using a SQL construct that the Postgres planner is not yet able to optimize. It may be possible to rewrite the query in a way that the planner is able to handle. For example, a subquery with an inline SELECT may not produce an efficient plan, but could possibly be rewritten using a LATERAL JOIN. French 454 characters edited Si la <command>SET ENABLE_SEQSCAN TO OFF;</command> n'aide pas votre requête, il se peut qu'elle utilise une construction SQL que le planificateur Postgres n'est pas encore en mesure d'optimiser. Il peut être possible de réécrire la requête de manière à ce que le planificateur soit en mesure de la traiter. Par exemple, une sous-requête avec un SELECT en ligne peut ne pas produire un plan efficace, mais peut être réécrite en utilisant un JOIN LATERAL. 2 weeks ago
anonymous Suggestion added postgis_branch_32 / using_postgis_dataman — French	English If <command>SET ENABLE_SEQSCAN TO OFF;</command> helps your query to run faster, your Postgres is likely not tuned for your hardware. If you find the planner wrong about the cost of sequential versus index scans try reducing the value of <varname>RANDOM_PAGE_COST</varname> in <code>postgresql.conf</code>, or use <command>SET RANDOM_PAGE_COST TO 1.1;</command>. The default value for <varname>RANDOM_PAGE_COST</varname> is 4.0. Try setting it to 1.1 (for SSD) or 2.0 (for fast magnetic disks). Decreasing the value makes the planner more likely to use index scans. French 702 characters edited Si <command>SET ENABLE_SEQSCAN TO OFF;</command> aide votre requête à s'exécuter plus rapidement, votre Postgres n'est probablement pas adapté à votre matériel. Si vous trouvez que le planificateur se trompe sur le coût des balayages séquentiels par rapport aux balayages d'index, essayez de réduire la valeur de <varname>RANDOM_PAGE_COST</varname> dans <code>postgresql.conf</code>, ou utilisez <command>SET RANDOM_PAGE_COST TO 1.1;</command>. La valeur par défaut de <varname>RANDOM_PAGE_COST</varname> est 4.0. Essayez de la fixer à 1.1 (pour les disques SSD) ou à 2.0 (pour les disques magnétiques rapides). En diminuant la valeur, le planificateur est plus enclin à utiliser les balayages d'index. 2 weeks ago
anonymous Suggestion added postgis_branch_32 / using_postgis_dataman — French	English If vacuuming does not help, you can temporarily force the planner to use the index information by using the command <command>SET ENABLE_SEQSCAN TO OFF;</command>. This way you can check whether the planner is at all able to generate an index-accelerated query plan for your query. You should only use this command for debugging; generally speaking, the planner knows better than you do about when to use indexes. Once you have run your query, do not forget to run <command>SET ENABLE_SEQSCAN TO ON;</command> so that the planner will operate normally for other queries. French 673 characters edited Si vacuum ne suffit pas, vous pouvez temporairement forcer le planificateur à utiliser les informations d'index en utilisant la commande <command>SET ENABLE_SEQSCAN TO OFF;</command>. De cette façon, vous pouvez vérifier si le planificateur est capable de générer un plan de requête accéléré par l'index pour votre requête. Vous ne devez utiliser cette commande qu'à des fins de débogage ; en règle générale, le planificateur sait mieux que vous quand utiliser les index. Une fois que vous avez exécuté votre requête, n'oubliez pas de lancer la commande <command>SET ENABLE_SEQSCAN TO ON;</command> afin que le planificateur fonctionne normalement pour les autres requêtes. 2 weeks ago
anonymous Suggestion added postgis_branch_32 / using_postgis_dataman — French	English You should regularly vacuum your databases anyways. Many PostgreSQL DBAs run <command>VACUUM</command> as an off-peak cron job on a regular basis. French 243 characters edited Vous devriez de toute façon vacuum régulièrement vos bases de données. De nombreux administrateurs de bases de données PostgreSQL exécutent <command>VACUUM</command> en tant que tâche cron en dehors des heures de pointe sur une base régulière. 2 weeks ago
anonymous Suggestion added postgis_branch_32 / using_postgis_dataman — French	English Make sure statistics are gathered about the number and distributions of values in a table, to provide the query planner with better information to make decisions around index usage. <command>VACUUM ANALYZE</command> will compute both. French 303 characters edited Assurez-vous que des statistiques sont collectées sur le nombre et la distribution des valeurs dans une table, afin de fournir au planificateur de requêtes de meilleures informations pour prendre des décisions concernant l'utilisation de l'index. La <command>VACUUM ANALYZE</command> calculera les deux. 2 weeks ago
anonymous Suggestion added postgis_branch_32 / using_postgis_dataman — French	English Examine the query plan and check your query actually computes the thing you need. An erroneous JOIN, either forgotten or to the wrong table, can unexpectedly retrieve table records multiple times. To get the query plan, execute with <code>EXPLAIN</code> in front of the query. French 330 characters edited Examinez le plan de requête et vérifiez que votre requête calcule effectivement ce dont vous avez besoin. Un JOIN erroné, oublié ou vers la mauvaise table, peut récupérer plusieurs fois des enregistrements de la table de manière inattendue. Pour obtenir le plan de la requête, exécutez avec <code>EXPLAIN</code> devant la requête. 2 weeks ago
anonymous Suggestion added postgis_branch_32 / using_postgis_dataman — French	English If you find your spatial indexes are not being used, there are a few things you can do: French 110 characters edited Si vous constatez que vos index spatiaux ne sont pas utilisés, il y a plusieurs choses que vous pouvez faire : 2 weeks ago
anonymous Suggestion added postgis_branch_32 / using_postgis_dataman — French	English Ordinarily, indexes invisibly speed up data access: once an index is built, the PostgreSQL query planner automatically decides when to use it to improve query performance. But there are some situations where the planner does not choose to use existing indexes, so queries end up using slow sequential scans instead of a spatial index. French 437 characters edited Normalement, les index accélèrent de manière invisible l'accès aux données : une fois qu'un index est construit, le planificateur de requêtes de PostgreSQL décide automatiquement quand l'utiliser pour améliorer les performances de la requête. Mais dans certaines situations, le planificateur ne choisit pas d'utiliser les index existants, et les requêtes finissent par utiliser des balayages séquentiels lents au lieu d'un index spatial. 2 weeks ago
anonymous Suggestion added postgis_branch_32 / using_postgis_dataman — French	English Tuning Index Usage French 40 characters edited Optimisation de l'utilisation de l'index 2 weeks ago

Browse all translation changes

Quick downloads

500	File in original format as translated in the repository	gettext PO file
500	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
418	Unfinished 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-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