Fix handling of pg_type.typdefault per bug report from Dave Blasby.
If there's anyone out there who's actually using datatype-defined default values, this will be an incompatible change in behavior ... but the old behavior was so broken that I doubt anyone was using it.
Showing
- doc/src/sgml/catalogs.sgml 9 additions, 3 deletionsdoc/src/sgml/catalogs.sgml
- src/backend/catalog/heap.c 8 additions, 11 deletionssrc/backend/catalog/heap.c
- src/backend/catalog/pg_type.c 21 additions, 20 deletionssrc/backend/catalog/pg_type.c
- src/backend/commands/define.c 9 additions, 11 deletionssrc/backend/commands/define.c
- src/backend/optimizer/prep/preptlist.c 36 additions, 27 deletionssrc/backend/optimizer/prep/preptlist.c
- src/backend/utils/cache/lsyscache.c 31 additions, 61 deletionssrc/backend/utils/cache/lsyscache.c
- src/bin/pg_dump/pg_dump.c 16 additions, 6 deletionssrc/bin/pg_dump/pg_dump.c
- src/include/catalog/pg_type.h 26 additions, 5 deletionssrc/include/catalog/pg_type.h
- src/include/utils/lsyscache.h 2 additions, 2 deletionssrc/include/utils/lsyscache.h
- src/test/regress/expected/create_type.out 25 additions, 0 deletionssrc/test/regress/expected/create_type.out
- src/test/regress/sql/create_type.sql 26 additions, 0 deletionssrc/test/regress/sql/create_type.sql
Loading
Please register or sign in to comment