postgis/PostGIS Manual — Portuguese (Brazil) @ OSGeo Weblate: constraint

Zen

	English	Portuguese (Brazil)	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>.
	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 ).
	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:
	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 :
	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 :
	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 :
	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.
	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>.
	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.
	In addition to the Postgres settings, PostGIS has some custom settings which are listed in <xref linkend="PostGIS_GUC"/>.
	Startup
	These settings are configured in <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.
	shared_buffers
	Default: ~128MB in PostgreSQL 9.6
	Set to about 25% to 40% of available RAM. On windows you may not be able to set as high.
	<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.
	Default: 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
	Default: 1-4MB
	Adjust up for large dbs, complex queries, lots of RAM
	Adjust down for many concurrent users or low RAM.
	If you have lots of RAM and few developers:
	<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.

Loading…

None

Automatically translated

English

Portuguese (Brazil) 20 characters edited Current translation Needs editing

2 years ago

None

String updated in the repository

English

Portuguese (Brazil) 0 characters edited Empty

2 years ago

Browse all string changes

Things to check

Unchanged translation

Source and translation are identical

Reset

Glossary

English	Portuguese (Brazil)
constraint_exclusion	constraint_exclusion	Glossary
constraint_exclusion	constraint_exclusion	Glossary

String information

Source string description

Tag: link

Labels

Automatically translated

Flags

no-c-format

String age

2 years ago

Last updated

2 years ago

Source string age

2 years ago

Translation file

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