More code review for rangetypes patch.
authorTom Lane <tgl@sss.pgh.pa.us>
Mon, 21 Nov 2011 21:19:53 +0000 (16:19 -0500)
committerTom Lane <tgl@sss.pgh.pa.us>
Mon, 21 Nov 2011 21:19:53 +0000 (16:19 -0500)
commita4ffcc8e115ed637f69ecb0295d78cc97f08a483
tree035ed76e98abd9c42c7294c2baa9db36f7f38a61
parent9b97b7f8356c63ea0b6704718d75ea01ec3035bf
More code review for rangetypes patch.

Fix up some infelicitous coding in DefineRange, and add some missing error
checks.  Rearrange operator strategy number assignments for GiST anyrange
opclass so that they don't make such a mess of opr_sanity's table of
operator names associated with different strategy numbers.  Assign
hopefully-temporary selectivity estimators to range operators that didn't
have one --- poor as the estimates are, they're still a lot better than the
default 0.5 estimate, and they'll shut up the opr_sanity test that wants to
see selectivity estimators on all built-in operators.
src/backend/commands/typecmds.c
src/backend/utils/adt/rangetypes_gist.c
src/include/catalog/catversion.h
src/include/catalog/pg_amop.h
src/include/catalog/pg_operator.h
src/test/regress/expected/opr_sanity.out
src/test/regress/expected/plpgsql.out
src/test/regress/expected/rangetypes.out
src/test/regress/sql/opr_sanity.sql
src/test/regress/sql/plpgsql.sql
src/test/regress/sql/rangetypes.sql