↑↓ select ↵ open ⌫ change scope Open full search

PG.CENTER connects PostgreSQL documentation, reference, and ecosystem knowledge. Maintained by Pigsty.

Wiki / Operator Families / GiST classes

gist/poly_ops (class)

GiST operator class for polygon; member of poly_ops.

Reading PostgreSQL 18.6.

Description

GiST operator class for polygon; member of poly_ops.

Object kind
Operator class
Index AM
GiST
Input type
polygon
Stored key type
box
Default class
yes

Usage

gist/poly_ops

Operator classes and families

An index definition can specify an operator class for each column of an index.

The operator class identifies the operators to be used by the index for that column. For example, a B-tree index on the type int4 would use the int4_ops class; this operator class includes comparison functions for values of type int4 . In practice the default operator class for the column's data type is usually sufficient. The main reason for having operator classes is that for some data types, there could be more than one meaningful index behavior. For example, we might want to sort a complex-number data type either by absolute value or by real part. We could do this by defining two operator classes for the data type and then selecting the proper class when making an index. The operator class determines the basic sort ordering (which can then be modified by adding sort options COLLATE , ASC / DESC and/or NULLS FIRST / NULLS LAST ).

There are also some built-in operator classes besides the default ones:

Family operator strategies

Operator overloadStrategyPurposeOrdering familyMembership scopeSource description
<<(polygon,polygon)1searchClass input pairis left of
&<(polygon,polygon)2searchClass input pairoverlaps or is left of
&&(polygon,polygon)3searchClass input pairoverlaps
&>(polygon,polygon)4searchClass input pairoverlaps or is right of
>>(polygon,polygon)5searchClass input pairis right of
~=(polygon,polygon)6searchClass input pairsame as
@>(polygon,polygon)7searchClass input paircontains
<@(polygon,polygon)8searchClass input pairis contained by
&<|(polygon,polygon)9searchClass input pairoverlaps or is below
<<|(polygon,polygon)10searchClass input pairis below
|>>(polygon,polygon)11searchClass input pairis above
|&>(polygon,polygon)12searchClass input pairoverlaps or is above
<->(polygon,point)15orderingfloat_opsFamily memberdistance between

Family support functions

Support numberLeft typeRight typeFunction signatureResult type
1polygonpolygongist_poly_consistent(internal,polygon,int2,oid,internal)bool
2polygonpolygongist_box_union(internal,internal)box
3polygonpolygongist_poly_compress(internal)internal
5polygonpolygongist_box_penalty(internal,internal,internal)internal
6polygonpolygongist_box_picksplit(internal,internal)internal
7polygonpolygongist_box_same(box,box,internal)internal
8polygonpolygongist_poly_distance(internal,polygon,int2,oid,internal)float8
12anyanygist_translate_cmptype_common(int4)int2

Classes in this family

ClassInput typeKey typeDefault
poly_opspolygonboxyes

Related entries

Documentation and source

Source build
Version
18.6
Build
https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2
Source fingerprint
555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f

Compare versions

PostgreSQL 13 → 14: changed.

--- PostgreSQL 13
+++ PostgreSQL 14
@@ -73,26 +73,6 @@
       "family": "poly_ops",
       "left_type": "polygon",
       "method": "gist",
-      "operator": "~(polygon,polygon)",
-      "purpose": "search",
-      "right_type": "polygon",
-      "sort_family": "",
-      "strategy": "13"
-    },
-    {
-      "family": "poly_ops",
-      "left_type": "polygon",
-      "method": "gist",
-      "operator": "@(polygon,polygon)",
-      "purpose": "search",
-      "right_type": "polygon",
-      "sort_family": "",
-      "strategy": "14"
-    },
-    {
-      "family": "poly_ops",
-      "left_type": "polygon",
-      "method": "gist",
       "operator": "&<(polygon,polygon)",
       "purpose": "search",
       "right_type": "polygon",

Compares recorded interfaces and attributes. Source fingerprints and build metadata are excluded; an absent sample is not proof of the introduction or removal release.

Related entries

Export JSON · Back to Operator Families · Recorded in PostgreSQL 10 through 20; the first sample is not necessarily its introduction.