be6fcb671e
Improve Range Types and Exclusion Constraints example.
...
Make the examples self-contained to avoid confusion. Per bug report
8367 from KOIZUMI Satoru.
2013-09-04 23:30:27 -07:00
ae7363999f
Mention in docs that you can create SP-GiST indexes on range types.
...
This is new in 9.3devel.
2013-04-22 21:51:14 +03:00
8b6b50a34d
Fix typo in example.
2012-08-23 11:58:11 +03:00
f1438cf5c6
Documentation style improvements
2012-06-08 10:29:12 +03:00
5baf6da717
Documentation spell and markup checking
2012-06-08 00:06:20 +03:00
604d4c4c95
Some more editing of the range-types documentation.
...
Be more thorough about specifying the expectations for canonical and
subtype_diff functions, and move that info to the same place.
2011-11-23 19:13:56 -05:00
df73584431
Remove zero- and one-argument range constructor functions.
...
Per discussion, the zero-argument forms aren't really worth the catalog
space (just write 'empty' instead). The one-argument forms have some use,
but they also have a serious problem with looking too much like functional
cast notation; to the point where in many real use-cases, the parser would
misinterpret what was wanted.
Committing this as a separate patch, with the thought that we might want
to revert part or all of it if we can think of some way around the cast
ambiguity.
2011-11-22 20:45:05 -05:00
a1a233af66
Further review of range-types patch.
...
Lots of documentation cleanup today, and still more type_sanity tests.
2011-11-18 18:24:32 -05:00
fbf99d2f16
Adjust range type docs for some last-minute changes I made to the patch.
...
non_empty(anyrange) function was removed, empty(anyrange) was renamed to
isempty(anyrange), and !? operators were removed.
2011-11-08 09:42:32 +02:00
4429f6a9e3
Support range data types.
...
Selectivity estimation functions are missing for some range type operators,
which is a TODO.
Jeff Davis
2011-11-03 13:42:15 +02:00
Jeff Davis
Heikki Linnakangas
Peter Eisentraut
Tom Lane