-
- Downloads
Fix the problem that creating a user-defined type named _foo, followed by one
named foo, would work but the other ordering would not. If a user-specified type or table name collides with an existing auto-generated array name, just rename the array type out of the way by prepending more underscores. This should not create any backward-compatibility issues, since the cases in which this will happen would have failed outright in prior releases. Also fix an oversight in the arrays-of-composites patch: ALTER TABLE RENAME renamed the table's rowtype but not its array type.
Showing
- doc/src/sgml/ref/create_type.sgml 22 additions, 13 deletionsdoc/src/sgml/ref/create_type.sgml
- src/backend/catalog/heap.c 26 additions, 3 deletionssrc/backend/catalog/heap.c
- src/backend/catalog/pg_type.c 96 additions, 16 deletionssrc/backend/catalog/pg_type.c
- src/backend/commands/tablecmds.c 7 additions, 5 deletionssrc/backend/commands/tablecmds.c
- src/backend/commands/typecmds.c 51 additions, 3 deletionssrc/backend/commands/typecmds.c
- src/include/catalog/pg_type.h 6 additions, 3 deletionssrc/include/catalog/pg_type.h
- src/test/regress/expected/arrays.out 23 additions, 0 deletionssrc/test/regress/expected/arrays.out
- src/test/regress/sql/arrays.sql 20 additions, 0 deletionssrc/test/regress/sql/arrays.sql
Loading
Please register or sign in to comment