postgis-workshop/indexing — Spanish @ OSGeo Weblate: `ST_Equals <http://postgis.net/docs/ST_Equals.html>`

Translation

English

Spanish

Needs editing

Skip

	English	Spanish	Actions
	`ST_Intersects <http://postgis.net/docs/ST_Intersects.html>`_	`ST_Intersects <http://postgis.net/docs/ST_Intersects.html>`_,
	`ST_Contains <http://postgis.net/docs/ST_Contains.html>`_	`ST_Contains <http://postgis.net/docs/ST_Contains.html>`_,
	`ST_Within <http://postgis.net/docs/ST_Within.html>`_	`ST_Within <http://postgis.net/docs/ST_Within.html>`_,
	`ST_DWithin <http://postgis.net/docs/ST_DWithin.html>`_	`ST_DWithin <http://postgis.net/docs/ST_DWithin.html>`_,
	`ST_ContainsProperly <http://postgis.net/docs/ST_ContainsProperly.html>`_	`ST_ContainsProperly <http://postgis.net/docs/ST_ContainsProperly.html>`_,
	`ST_CoveredBy <http://postgis.net/docs/ST_CoveredBy.html>`_	`ST_CoveredBy <http://postgis.net/docs/ST_CoveredBy.html>`_,
	`ST_Covers <http://postgis.net/docs/ST_Covers.html>`_	`ST_Covers <http://postgis.net/docs/ST_Covers.html>`_,
	`ST_Overlaps <http://postgis.net/docs/ST_Overlaps.html>`_	`ST_Overlaps <http://postgis.net/docs/ST_Overlaps.html>`_,
	`ST_Crosses <http://postgis.net/docs/ST_Crosses.html>`_	`ST_Crosses <http://postgis.net/docs/ST_Crosses.html>`_,
	`ST_DFullyWithin <http://postgis.net/docs/ST_DFullyWithin.html>`_	`ST_DFullyWithin <http://postgis.net/docs/ST_DFullyWithin.html>`_,
	`ST_3DIntersects <http://postgis.net/docs/ST_3DIntersects.html>`_	`ST_3DIntersects <http://postgis.net/docs/ST_3DIntersects.html>`_,
	`ST_3DDWithin <http://postgis.net/docs/ST_3DDWithin.html>`_	`ST_3DDWithin <http://postgis.net/docs/ST_3DDWithin.html>`_,
	`ST_3DDFullyWithin <http://postgis.net/docs/ST_3DDFullyWithin.html>`_	`ST_3DDFullyWithin <http://postgis.net/docs/ST_3DDFullyWithin.html>`_,
	`ST_LineCrossingDirection <http://postgis.net/docs/ST_LineCrossingDirection.html>`_	`ST_LineCrossingDirection <http://postgis.net/docs/ST_LineCrossingDirection.html>`_,
	`ST_OrderingEquals <http://postgis.net/docs/ST_OrderingEquals.html>`_	`ST_OrderingEquals <http://postgis.net/docs/ST_OrderingEquals.html>`_,
	`ST_Equals <http://postgis.net/docs/ST_Equals.html>`_	`ST_Equals <http://postgis.net/docs/ST_Equals.html>`_.
	The first four are the ones most commonly used in queries, and `ST_DWithin <http://postgis.net/docs/ST_DWithin.html>`_ is very important for doing "within a distance" or "within a radius" style queries while still getting a performance boost from the index.	Los cuatro primeros son los más utilizados en consultas y `ST_DWithin <http://postgis.net/docs/ST_DWithin.html>`_ es muy importante para hacer consultas tipo "dentro de una distancia" o "dentro de un radio" consiguiendo un rendimiento óptimo por el índice.
	In order to add index acceleration to other functions that are not in this list (most commonly, `ST_Relate <http://postgis.net/docs/ST_Relate.html>`_) add an index-only clause as described below.	Para añadir aceleración por índices a otras funciones que no están en esta lista (la más habitual, `ST_Relate <http://postgis.net/docs/ST_Relate.html>`_) hay que añadir una clausula de indexación como la descrita debajo.
	Index-Only Queries
	Most of the commonly used functions in PostGIS (:command:`ST_Contains`, :command:`ST_Intersects`, :command:`ST_DWithin`, etc) include an index filter automatically. But some functions (e.g., :command:`ST_Relate`) do not include an index filter.	La mayoría de las funciones usadas comunmente en PostGIS (:command:`ST_Contains`, :command:`ST_Intersects`, :command:`ST_DWithin`, etc) incluyen un filtrado por índice automáticamente. Pero algunas funciones (p. ej.: :command:`ST_Relate`) no incluyen este filtrado.
	To do a bounding-box search using the index (and no filtering), make use of the :command:`&&` operator. For geometries, the :command:`&&` operator means "bounding boxes overlap or touch" in the same way that for numbers the :command:`=` operator means "values are the same".
	Let's compare an index-only query for the population of the 'West Village' to a more exact query. Using :command:`&&` our index-only query looks like the following:
	Now let's do the same query using the more exact :command:`ST_Intersects` function.	Ahora, hagamos la misma consulta usando la función :command:`ST_Intersects`, que es más exacta.
	A much lower answer! The first query summed up every block whose bounding box intersects the neighborhood's bounding box; the second query only summed up those blocks that intersect the neighborhood itself.
	Analyzing
	The PostgreSQL query planner intelligently chooses when to use or not to use indexes to evaluate a query. Counter-intuitively, it is not always faster to do an index search: if the search is going to return every record in the table, traversing the index tree to get each record will actually be slower than just sequentially reading the whole table from the start.
	Knowing the size of the query rectangle is not enough to pin down whether a query will return a large number or small number of records. Below, the red square is small, but will return many more records than the blue square.
	In order to figure out what situation it is dealing with (reading a small part of the table versus reading a large portion of the table), PostgreSQL keeps statistics about the distribution of data in each indexed table column. By default, PostgreSQL gathers statistics on a regular basis. However, if you dramatically change the contents of your table within a short period of time, the statistics will not be up-to-date.
	To ensure the statistics match your table contents, it is wise the to run the ``ANALYZE`` command after bulk data loads and deletes in your tables. This force the statistics system to gather data for all your indexed columns.
	The ``ANALYZE`` command asks PostgreSQL to traverse the table and update its internal statistics used for query plan estimation (query plan analysis will be discussed later).
	Vacuuming

Loading…

dmateos

Translation changed

English

Spanish 1 character edited Current translation

2 years ago

dmateos

Translation added

English

Spanish 54 characters edited

2 years ago

Browse all string changes

Things to check

Mismatched full stop

Source and translation do not both end with a full stop

Reset

Glossary

English	Spanish
No related strings found in the glossary.

String information

Source string location

../../en/indexing.rst:93

String age

3 years ago

Last updated

a year ago

Source string age

3 years ago

Translation file

postgis-intro/sources/locale/es/LC_MESSAGES/indexing.po, string 36