Remove zero- and one-argument range constructor functions.
authorTom Lane <tgl@sss.pgh.pa.us>
Wed, 23 Nov 2011 01:45:05 +0000 (20:45 -0500)
committerTom Lane <tgl@sss.pgh.pa.us>
Wed, 23 Nov 2011 01:45:05 +0000 (20:45 -0500)
commitdf73584431e7edb1dd76578777bd0fcc17b916a1
tree3fb50fe824636a99d0af48ea153bfb362475c84b
parentcddc819e45010492da00164d225a749661f43aef
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.
doc/src/sgml/rangetypes.sgml
src/backend/commands/typecmds.c
src/backend/utils/adt/rangetypes.c
src/include/catalog/catversion.h
src/include/catalog/pg_proc.h
src/include/utils/rangetypes.h
src/test/regress/expected/rangetypes.out
src/test/regress/sql/rangetypes.sql