postgis/PostGIS Manual — Chinese (Simplified) @ OSGeo Weblate: constraint

Zen

	English	Chinese (Simplified)	Actions
	Errors may arise in the following cases:	在以下情况下可能会发生错误：
	Some of your views or functions make use of deprecated PostGIS objects. In order to fix this you may try loading <filename>legacy.sql</filename> script prior to restore or you'll have to restore to a version of PostGIS which still contains those objects and try a migration again after porting your code. If the <filename>legacy.sql</filename> way works for you, don't forget to fix your code to stop using deprecated functions and drop them loading <filename>uninstall_legacy.sql</filename>.	您的某些视图或函数使用已弃用的 PostGIS 对象。为了解决这个问题，您可以尝试在恢复之前加载 <filename>legacy.sql</filename> 脚本，或者您必须恢复到仍包含这些对象的 PostGIS 版本，并在移植代码后再次尝试迁移。如果 <filename>legacy.sql</filename> 方式适合您，请不要忘记修复您的代码以停止使用已弃用的函数并将其加载 <filename>uninstall_legacy.sql</filename>。
	Some custom records of spatial_ref_sys in dump file have an invalid SRID value. Valid SRID values are bigger than 0 and smaller than 999000. Values in the 999000.999999 range are reserved for internal use while values > 999999 can't be used at all. All your custom records with invalid SRIDs will be retained, with those > 999999 moved into the reserved range, but the spatial_ref_sys table would lose a check constraint guarding for that invariant to hold and possibly also its primary key ( when multiple invalid SRIDS get converted to the same reserved SRID value ).	一些在转储文件中的自定义空间参考系统记录具有无效的SRID值。有效的SRID值应大于0且小于999000。值在999000.999999范围内被保留供内部使用，而大于999999的值则根本不能使用。所有具有无效SRID的自定义记录将被保留，其中大于999999的值将被移动到保留范围内，但空间_ref_sys表将失去维护该不变条件的检查约束，可能还会失去其主键（当多个无效的SRID值转换为相同的保留SRID值时）。
	In order to fix this you should copy your custom SRS to a SRID with a valid value (maybe in the 910000..910999 range), convert all your tables to the new srid (see <xref linkend="UpdateGeometrySRID"/>), delete the invalid entry from spatial_ref_sys and re-construct the check(s) with:	为了解决此问题，您应该将自定义SRS复制到具有有效值的 SRID（可能在 910000..910999 范围），将所有表转换为新的 srid （请参阅<xref linkend="UpdateGeometrySRID"/>），删除无效的从spatial_ref_sys输入并重建检查：
	If you are upgrading an old database containing french <link xlink:href="https://en.wikipedia.org/wiki/Institut_g%C3%A9ographique_national"> IGN </link> cartography, you will have probably SRIDs out of range and you will see, when importing your database, issues like this :	如果要升级包含法国 <link xlink:href="https://en.wikipedia.org/wiki/Institut_g%C3%A9ographique_national"> IGN </link> 映射的旧数据库，则可能会超出 SRID 的范围，并在导入数据库时遇到以下问题：
	In this case, you can try following steps : first throw out completely the IGN from the sql which is resulting from postgis_restore. So, after having run :	在这种情况下，您可以尝试以下步骤：完全丢弃最初从 SQL postgis_restore中产生的 IGN。为此，请运行以下命令：
	run this command :	运行以下命令：
	Create then your newdb, activate the required Postgis extensions, and insert properly the french system IGN with : <link xlink:href="https://raw.githubusercontent.com/Remi-C/IGN_spatial_ref_for_PostGIS/master/Put_IGN_SRS_into_Postgis.sql"> this script </link> After these operations, import your data :	之后，生成一个新数据库，启用必要的 PostGIS 扩展，并确保使用此 <link xlink:href="https://raw.githubusercontent.com/Remi-C/IGN_spatial_ref_for_PostGIS/master/Put_IGN_SRS_into_Postgis.sql"> 脚本</link>插入法语 IGN 系统。完成这些过程后，按如下方式导入数据：
	Performance Tuning	性能调优
	Tuning for PostGIS performance is much like tuning for any PostgreSQL workload. The only additional consideration is that geometries and rasters are usually large, so memory-related optimizations generally have more of an impact on PostGIS than other types of PostgreSQL queries.	PostGIS 性能的调优与任何 PostgreSQL 工作负载的调优非常相似。唯一需要额外考虑的是，几何图形和栅格通常很大，因此与内存相关的优化通常对 PostGIS 的影响比其他类型的 PostgreSQL 查询更大。
	For general details about optimizing PostgreSQL, refer to <link xlink:href="https://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server">Tuning your PostgreSQL Server</link>.	有关优化 PostgreSQL 的一般详细信息，请参阅 <link xlink:href="https://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server">调整 PostgreSQL 服务器</link>。
	For PostgreSQL 9.4+ configuration can be set at the server level without touching <code>postgresql.conf</code> or <code>postgresql.auto.conf</code> by using the <code>ALTER SYSTEM</code> command.	对于 PostgreSQL 9.4+，可以使用<code> ALTER SYSTEM</code> 命令在服务器级别设置配置，而无需触及 <code>postgresql.conf</code> 或 <code>postgresql.auto.conf</code>。
	In addition to the Postgres settings, PostGIS has some custom settings which are listed in <xref linkend="PostGIS_GUC"/>.	除了 Postgres 设置之外，PostGIS 还有一些自定义设置，请参见<xref linkend="PostGIS_GUC"/>。
	Startup	启动
	These settings are configured in <code>postgresql.conf</code>:	这些设置在<code> postgresql.conf </code>中配置：
	constraint_exclusion	constraint_exclusion
	Default: partition	默认：分区
	This is generally used for table partitioning. The default for this is set to "partition" which is ideal for PostgreSQL 8.4 and above since it will force the planner to only analyze tables for constraint consideration if they are in an inherited hierarchy and not pay the planner penalty otherwise.	这通常用于表分区。默认设置为 "partition"，适用于 PostgreSQL 8.4 及更高版本，因为它将强制查询规划器仅在表处于继承层次结构中时分析约束考虑，否则将不会对规划器产生影响。
	shared_buffers	共享缓冲区
	Default: ~128MB in PostgreSQL 9.6	默认值：PostgreSQL 9.6 中约为 128MB
	Set to about 25% to 40% of available RAM. On windows you may not be able to set as high.	将其设置为可用RAM的约 25% 到 40%。在 Windows 上，您可能无法设置得那么高。
	<link xlink:href="https://www.postgresql.org/docs/current/static/runtime-config-resource.html#GUC-MAX-WORKER-PROCESSES">max_worker_processes</link> This setting is only available for PostgreSQL 9.4+. For PostgreSQL 9.6+ this setting has additional importance in that it controls the max number of processes you can have for parallel queries.	<link xlink:href="https://www.postgresql.org/docs/current/static/runtime-config-resource.html#GUC-MAX-WORKER-PROCESSES">max_worker_processes </link>此设置仅适用于 PostgreSQL 9.4 +。对于 PostgreSQL 9.6+，此设置具有额外的重要性，因为它控制并行查询可以拥有的最大进程数。
	Default: 8	默认值：8
	Sets the maximum number of background processes that the system can support. This parameter can only be set at server start.	设置系统可以支持的最大后台进程数。该参数只能在服务器启动时设置。
	Runtime	运行
	<link xlink:href="http://www.postgresql.org/docs/current/static/runtime-config-resource.html#GUC-WORK-MEM">work_mem</link> - sets the size of memory used for sort operations and complex queries	<link xlink:href="http://www.postgresql.org/docs/current/static/runtime-config-resource.html#GUC-WORK-MEM">work_mem</link> - 设置用于排序操作和复杂查询的内存大小
	Default: 1-4MB	默认：1-4MB
	Adjust up for large dbs, complex queries, lots of RAM	针对大型数据库、复杂查询、大量 RAM 进行调整
	Adjust down for many concurrent users or low RAM.	针对许多并发用户或 RAM 较低的情况进行下调。
	If you have lots of RAM and few developers:	如果您有大量 RAM 而开发人员很少：
	<link xlink:href="http://www.postgresql.org/docs/current/static/runtime-config-resource.html#GUC-MAINTENANCE-WORK-MEM">maintenance_work_mem</link> - the memory size used for VACUUM, CREATE INDEX, etc.	<link xlink:href="http://www.postgresql.org/docs/current/static/runtime-config-resource.html#GUC-MAINTENANCE-WORK-MEM">Maintenance_work_mem</link> - 用于 VACUUM、CREATE INDEX 等的内存大小。

Loading…

None

String updated in the repository

English

Chinese (Simplified) 20 characters edited Current translation Translated

8 months ago

Browse all string changes

Things to check

Unchanged translation

Source and translation are identical

Reset

Glossary

English	Chinese (Simplified)
constraint_exclusion	constraint_exclusion	Glossary
constraint_exclusion	constraint_exclusion	Glossary

String information

Source string description

Tag: link

Flags

no-c-format

String age

8 months ago

Last updated

8 months ago

Source string age

8 months ago

Translation file

doc/po/zh_Hans/postgis-manual.po, string 78