Flip the default typispreferred setting from true to false. This affects
commit4921cd5c8d9d3ad26cc07bd4fe5a00fd6b8f9957
authortgl <tgl>
Wed, 30 Jul 2008 19:35:13 +0000 (30 19:35 +0000)
committertgl <tgl>
Wed, 30 Jul 2008 19:35:13 +0000 (30 19:35 +0000)
treefe106bcc6ef07b8e6d65d51428667ae1a54ffee6
parent1c26209d49c7ee561ecd2f923dceaa2ca2cedaf5
Flip the default typispreferred setting from true to false.  This affects
only type categories in which the previous coding made *every* type
preferred; so there is no change in effective behavior, because the function
resolution rules only do something different when faced with a choice
between preferred and non-preferred types in the same category.  It just
seems safer and less surprising to have CREATE TYPE default to non-preferred
status ...
doc/src/sgml/ref/create_type.sgml
doc/src/sgml/typeconv.sgml
src/backend/catalog/heap.c
src/backend/commands/typecmds.c
src/bin/pg_dump/pg_dump.c
src/include/catalog/catversion.h
src/include/catalog/pg_type.h
src/test/regress/expected/create_type.out
src/test/regress/sql/create_type.sql