From 9effc4608e1f6d19546a0e0f64320f4b0dd10c3c Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Thu, 9 May 2024 12:19:43 -0400 Subject: Repair ALTER EXTENSION ... SET SCHEMA. It turns out that we broke this in commit e5bc9454e, because the code was assuming that no dependent types would appear among the extension's direct dependencies, and now they do. This isn't terribly hard to fix: just skip dependent types, expecting that we will recurse to them when we process the parent object (which should also be among the direct dependencies). But a little bit of refactoring is needed so that we can avoid duplicating logic about what is a dependent type. Although there is some testing of ALTER EXTENSION SET SCHEMA, it failed to cover interesting cases, so add more tests. Discussion: https://postgr.es/m/930191.1715205151@sss.pgh.pa.us --- src/backend/commands/extension.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/backend/commands/extension.c') diff --git a/src/backend/commands/extension.c b/src/backend/commands/extension.c index 77d8c9e1862..1643c8c69a0 100644 --- a/src/backend/commands/extension.c +++ b/src/backend/commands/extension.c @@ -2940,7 +2940,7 @@ AlterExtensionNamespace(const char *extensionName, const char *newschema, Oid *o /* * If not all the objects had the same old namespace (ignoring any - * that are not in namespaces), complain. + * that are not in namespaces or are dependent types), complain. */ if (dep_oldNspOid != InvalidOid && dep_oldNspOid != oldNspOid) ereport(ERROR, -- cgit v1.2.3