Fix failure of ALTER FOREIGN TABLE SET SCHEMA to move sequences. Ordinary ALTER TABLE SET SCHEMA will also move any owned sequences into the new schema. We failed to do likewise for foreign tables, because AlterTableNamespaceInternal believed that only certain relkinds could have indexes, owned sequences, or constraints. We could simply add foreign tables to that relkind list, but it seems likely that the same oversight could be made again in future. Instead let's remove the relkind filter altogether. These functions shouldn't cost much when there are no objects that they need to process, and surely this isn't an especially performance-critical case anyway.
Per bug #18407 from Vidushi Gupta. Back-patch to all supported branches. Discussion: https://postgr.es/m/18407-4fd07373d252c...@postgresql.org Branch ------ REL_14_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/66bbad581ce289fab8a55152987a223fe8795fee Modified Files -------------- src/backend/commands/tablecmds.c | 15 +++++---------- src/test/regress/expected/foreign_data.out | 29 +++++++++++++++++------------ src/test/regress/sql/foreign_data.sql | 2 ++ 3 files changed, 24 insertions(+), 22 deletions(-)