↑↓ select ↵ open ⌫ change scope Open full search

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

Wiki / Data Types / Geometric

point

geometric point on a plane

Reading PostgreSQL 18.6.

PG10–20 core source inventory. Casts and operator classes show explicitly declared relationships; absent rows do not rule out coercions or indexing through other mechanisms.

Definition

geometric point on a plane

point
Catalog name
pg_catalog.point
Type OID
600
Type kind
Base type
Declared length
16 bytes
Storage strategy
plain
Input function
point_in
Output function
point_out
Documented declaration
point
Storage Size
16 bytes
Manual description
Point on a plane
Representation
(x,y)

English manual

Read the complete manual section

Read the source definition

8.8. Geometric Types

Geometric data types represent two-dimensional spatial objects. Table 8.20 shows the geometric types available in PostgreSQL.

Table 8.20. Geometric Types

Name Storage Size Description Representation
point 16 bytes Point on a plane (x,y)
line 24 bytes Infinite line {A,B,C}
lseg 32 bytes Finite line segment [(x1,y1),(x2,y2)]
box 32 bytes Rectangular box (x1,y1),(x2,y2)
path 16+16n bytes Closed path (similar to polygon) ((x1,y1),...)
path 16+16n bytes Open path [(x1,y1),...]
polygon 40+16n bytes Polygon (similar to closed path) ((x1,y1),...)
circle 24 bytes Circle <(x,y),r> (center point and radius)

In all these types, the individual coordinates are stored as double precision (float8) numbers.

A rich set of functions and operators is available to perform various geometric operations such as scaling, translation, rotation, and determining intersections. They are explained in Section 9.11.

8.8.1. Points

Points are the fundamental two-dimensional building block for geometric types. Values of type point are specified using either of the following syntaxes:

( x , y )
  x , y

where x and y are the respective coordinates, as floating-point numbers.

Points are output using the first syntax.

8.8.2. Lines

Lines are represented by the linear equation Ax + By + C = 0, where A and B are not both zero. Values of type line are input and output in the following form:

{ A, B, C }

Alternatively, any of the following forms can be used for input:

[ ( x1 , y1 ) , ( x2 , y2 ) ]
( ( x1 , y1 ) , ( x2 , y2 ) )
  ( x1 , y1 ) , ( x2 , y2 )
    x1 , y1   ,   x2 , y2

where (x1,y1) and (x2,y2) are two different points on the line.

8.8.3. Line Segments

Line segments are represented by pairs of points that are the endpoints of the segment. Values of type lseg are specified using any of the following syntaxes:

[ ( x1 , y1 ) , ( x2 , y2 ) ]
( ( x1 , y1 ) , ( x2 , y2 ) )
  ( x1 , y1 ) , ( x2 , y2 )
    x1 , y1   ,   x2 , y2

where (x1,y1) and (x2,y2) are the end points of the line segment.

Line segments are output using the first syntax.

8.8.4. Boxes

Boxes are represented by pairs of points that are opposite corners of the box. Values of type box are specified using any of the following syntaxes:

( ( x1 , y1 ) , ( x2 , y2 ) )
  ( x1 , y1 ) , ( x2 , y2 )
    x1 , y1   ,   x2 , y2

where (x1,y1) and (x2,y2) are any two opposite corners of the box.

Boxes are output using the second syntax.

Any two opposite corners can be supplied on input, but the values will be reordered as needed to store the upper right and lower left corners, in that order.

8.8.5. Paths

Paths are represented by lists of connected points. Paths can be open, where the first and last points in the list are considered not connected, or closed, where the first and last points are considered connected.

Values of type path are specified using any of the following syntaxes:

[ ( x1 , y1 ) , ... , ( xn , yn ) ]
( ( x1 , y1 ) , ... , ( xn , yn ) )
  ( x1 , y1 ) , ... , ( xn , yn )
  ( x1 , y1   , ... ,   xn , yn )
    x1 , y1   , ... ,   xn , yn

where the points are the end points of the line segments comprising the path. Square brackets ([]) indicate an open path, while parentheses (()) indicate a closed path. When the outermost parentheses are omitted, as in the third through fifth syntaxes, a closed path is assumed.

Paths are output using the first or second syntax, as appropriate.

8.8.6. Polygons

Polygons are represented by lists of points (the vertices of the polygon). Polygons are very similar to closed paths; the essential semantic difference is that a polygon is considered to include the area within it, while a path is not.

An important implementation difference between polygons and paths is that the stored representation of a polygon includes its smallest bounding box. This speeds up certain search operations, although computing the bounding box adds overhead while constructing new polygons.

Values of type polygon are specified using any of the following syntaxes:

( ( x1 , y1 ) , ... , ( xn , yn ) )
  ( x1 , y1 ) , ... , ( xn , yn )
  ( x1 , y1   , ... ,   xn , yn )
    x1 , y1   , ... ,   xn , yn

where the points are the end points of the line segments comprising the boundary of the polygon.

Polygons are output using the first syntax.

8.8.7. Circles

Circles are represented by a center point and radius. Values of type circle are specified using any of the following syntaxes:

< ( x , y ) , r >
( ( x , y ) , r )
  ( x , y ) , r
    x , y   , r

where (x,y) is the center point and r is the radius of the circle.

Circles are output using the first syntax.

Catalog attributes

Source bootstrap values for this build. See pg_type for field meanings. Header defaults are included; build-dependent constants remain symbolic. This is not a live-server measurement.

oid
600
descr
geometric point, format '(x,y)'
typacl
_null_
typlen
16
typelem
float8
typname
point
typsend
point_send
typtype
b
typalign
d
typarray
0
typbyval
f
typdelim
','
typinput
point_in
typmodin
-
typndims
0
typowner
POSTGRES
typrelid
0
typmodout
-
typoutput
point_out
typtypmod
-1
typanalyze
-
typdefault
_null_
typnotnull
f
typreceive
point_recv
typstorage
p
typbasetype
0
typcategory
G
typcollation
0
typisdefined
t
typnamespace
pg_catalog
typsubscript
raw_array_subscript_handler
typdefaultbin
_null_
array_type_oid
1017
typispreferred
f
array_type_name
_point

Catalog casts 5

Explicit pg_cast records involving this type. PostgreSQL also supports coercions outside pg_cast; an absent row does not prove that a conversion is impossible.

FromToContextMethodFunction
pointboxAssignmentFunctionbox(point)
lsegpointExplicitFunctionpoint(lseg)
boxpointExplicitFunctionpoint(box)
polygonpointExplicitFunctionpoint(polygon)
circlepointExplicitFunctionpoint(circle)

Operator overloads 52

Each operand signature is a separate overload. Catalog implementation functions and result types belong to the same source build.

OperatorLeft operandRight operandResultMeaningImplementation
>^pointpointbooldeprecated, use |>> insteadpoint_above
<<pointpointboolis left ofpoint_left
>>pointpointboolis right ofpoint_right
<^pointpointbooldeprecated, use <<| insteadpoint_below
~=pointpointboolsame aspoint_eq
<@pointboxboolpoint inside boxon_pb
@>boxpointboolcontainsbox_contain_pt
<@pointpathboolpoint within closed path, or point on open pathon_ppath
<->pointpointfloat8distance betweenpoint_distance
<->pointlinefloat8distance betweendist_pl
<->linepointfloat8distance betweendist_lp
<->pointlsegfloat8distance betweendist_ps
<->lsegpointfloat8distance betweendist_sp
<->pointboxfloat8distance betweendist_pb
<->boxpointfloat8distance betweendist_bp
<->pointpathfloat8distance betweendist_ppath
<->pathpointfloat8distance betweendist_pathp
<>pointpointboolnot equalpoint_ne
+pointpointpointadd points (translate)point_add
-pointpointpointsubtract points (translate)point_sub
*pointpointpointmultiply points (scale/rotate)point_mul
/pointpointpointdivide points (scale/rotate)point_div
+pathpointpathadd (translate path)path_add_pt
-pathpointpathsubtract (translate path)path_sub_pt
*pathpointpathmultiply (rotate/scale path)path_mul_pt
/pathpointpathdivide (rotate/scale path)path_div_pt
@>pathpointboolcontainspath_contain_pt
<@pointpolygonboolis contained bypt_contained_poly
@>polygonpointboolcontainspoly_contain_pt
<@pointcircleboolis contained bypt_contained_circle
@>circlepointboolcontainscircle_contain_pt
+boxpointboxadd point to box (translate)box_add
-boxpointboxsubtract point from box (translate)box_sub
*boxpointboxmultiply box by point (scale)box_mul
/boxpointboxdivide box by point (scale)box_div
?-pointpointboolhorizontally alignedpoint_horiz
?|pointpointboolvertically alignedpoint_vert
+circlepointcircleaddcircle_add_pt
-circlepointcirclesubtractcircle_sub_pt
*circlepointcirclemultiplycircle_mul_pt
/circlepointcircledividecircle_div_pt
<->pointcirclefloat8distance betweendist_pc
<->circlepointfloat8distance betweendist_cpoint
<->pointpolygonfloat8distance betweendist_ppoly
<->polygonpointfloat8distance betweendist_polyp
<@pointlineboolpoint on lineon_pl
<@pointlsegboolis contained byon_ps
##pointlinepointclosest point to A on Bclose_pl
##pointlsegpointclosest point to A on Bclose_ps
##pointboxpointclosest point to A on Bclose_pb
|>>pointpointboolis abovepoint_above
<<|pointpointboolis belowpoint_below

Operator classes 3

Operator classes whose declared input type matches this type. Polymorphic classes, casts and expression indexes can provide additional index paths; this list is not an exhaustive yes/no index-support test.

ClassIndex methodInput typeFamilyDefaultStorage type
point_opsgistpointgist/point_opsYesbox
quad_point_opsspgistpointspgist/quad_point_opsYesSame as input
kd_point_opsspgistpointspgist/kd_point_opsNoSame as input

Version comparison

PostgreSQL 17.11 → 18.6. Source build identifiers and prose are excluded from attribute changes.

No catalog or structured attribute changes between these samples.

The documentation also differs between these builds; inspect the versioned manual definitions.

Documentation and source

Build
18.6 · https://ftp.postgresql.org/pub/source/v18.6/postgresql-18.6.tar.bz2
Fingerprint
555610c24d53e4316da5b7d3fc25c279d96856d5e0e23ee308c328c5fa881d9f

Related entries

All Data Types · Download this version as JSON · The first recorded sample does not establish when a type was introduced.