Skip to content

Commit 7961cd4

Browse files
committed
Doc: small improvements in discussion of geometric data types.
State explicitly that the coordinates in our geometric data types are float8. Also explain that polygons store their bounding box. While here, fix the table of geometric data types to show type "line"'s size correctly: it's 24 bytes not 32. This has somehow escaped notice since that table was made in 1998. Per suggestion from Sebastian Skałacki. The size error seems important enough to justify back-patching. Discussion: https://postgr.es/m/172000045661.706.1822177575291548794@wrigleys.postgresql.org
1 parent 0e3df0e commit 7961cd4

File tree

1 file changed

+16
-3
lines changed

1 file changed

+16
-3
lines changed

doc/src/sgml/datatype.sgml

Lines changed: 16 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3350,7 +3350,7 @@ SELECT person.name, holidays.num_weeks FROM person, holidays
33503350
</row>
33513351
<row>
33523352
<entry><type>line</type></entry>
3353-
<entry>32 bytes</entry>
3353+
<entry>24 bytes</entry>
33543354
<entry>Infinite line</entry>
33553355
<entry>{A,B,C}</entry>
33563356
</row>
@@ -3394,6 +3394,11 @@ SELECT person.name, holidays.num_weeks FROM person, holidays
33943394
</tgroup>
33953395
</table>
33963396

3397+
<para>
3398+
In all these types, the individual coordinates are stored as
3399+
<type>double precision</type> (<type>float8</type>) numbers.
3400+
</para>
3401+
33973402
<para>
33983403
A rich set of functions and operators is available to perform various geometric
33993404
operations such as scaling, translation, rotation, and determining
@@ -3584,8 +3589,16 @@ SELECT person.name, holidays.num_weeks FROM person, holidays
35843589
<para>
35853590
Polygons are represented by lists of points (the vertexes of the
35863591
polygon). Polygons are very similar to closed paths; the essential
3587-
difference is that a polygon is considered to include the area
3588-
within it, while a path is not.
3592+
semantic difference is that a polygon is considered to include the
3593+
area within it, while a path is not.
3594+
</para>
3595+
3596+
<para>
3597+
An important implementation difference between polygons and
3598+
paths is that the stored representation of a polygon includes its
3599+
smallest bounding box. This speeds up certain search operations,
3600+
although computing the bounding box adds overhead while constructing
3601+
new polygons.
35893602
</para>
35903603

35913604
<para>

0 commit comments

Comments
 (0)