mirror/postgresql
2
0
Fork 0
mirror of https://git.postgresql.org/git/postgresql.git synced 2024-11-27 07:21:09 +08:00
Code Issues Packages Projects Releases Wiki Activity

Doc: small improvements in discussion of geometric data types.

Browse Source 
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
This commit is contained in:
Tom Lane 2024-07-04 13:23:32 -04:00
parent fbe039fa61
commit cfac450378
1 changed files with 17 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
doc/src/sgml/datatype.sgml
View File

@ -3264,7 +3264,7 @@ SELECT person.name, holidays.num_weeks FROM person, holidays
</row>
<row>
<entry><type>line</type></entry>
<entry>32 bytes</entry>
<entry>24 bytes</entry>
<entry>Infinite line</entry>
<entry>{A,B,C}</entry>
</row>
@ -3308,6 +3308,11 @@ SELECT person.name, holidays.num_weeks FROM person, holidays
</tgroup>
</table>
<para>
In all these types, the individual coordinates are stored as
<type>double precision</type> (<type>float8</type>) numbers.
</para>
<para>
A rich set of functions and operators is available to perform various geometric
operations such as scaling, translation, rotation, and determining
@ -3497,8 +3502,17 @@ SELECT person.name, holidays.num_weeks FROM person, holidays
<para>
Polygons are represented by lists of points (the vertexes of the
polygon). Polygons are very similar to closed paths, but are
stored differently and have their own set of support routines.
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.
</para>
<para>
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.
</para>
<para>