aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistbuild.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2023-03-27 15:04:02 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2023-03-27 15:04:02 -0400
commit29a20ff0617ab60acbb8d71b6b59f9035c86a4f8 (patch)
tree8c32775a51249580dac9061912f10bbb35493872 /src/backend/access/gist/gistbuild.c
parent1bbbe14607c3590c977dc0aeddfdc10680f6bd39 (diff)
downloadpostgresql-29a20ff0617ab60acbb8d71b6b59f9035c86a4f8.tar.gz
postgresql-29a20ff0617ab60acbb8d71b6b59f9035c86a4f8.zip
Reject attempts to alter composite types used in indexes.
find_composite_type_dependencies() ignored indexes, which is a poor decision because an expression index could have a stored column of a composite (or other container) type even when the underlying table does not. Teach it to detect such cases and error out. We have to work a bit harder than for other relations because the pg_depend entry won't identify the specific index column of concern, but it's not much new code. This does not address bug #17872's original complaint that dropping a column in such a type might lead to violations of the uniqueness property that a unique index is supposed to ensure. That seems of much less concern to me because it won't lead to crashes. Per bug #17872 from Alexander Lakhin. Back-patch to all supported branches. Discussion: https://postgr.es/m/17872-d0fbb799dc3fd85d@postgresql.org
Diffstat (limited to 'src/backend/access/gist/gistbuild.c')
0 files changed, 0 insertions, 0 deletions