Install extensions in the service's own schema

[mahlunar]

Problem

installExtensions created extensions with WITH SCHEMA <serviceCredentials.Name>, i.e. the database name. For shared databases the database name is the name of another service's schema, so extensions could be installed into a schema belonging to a different service. In almost all cases, this changes nothing as normally only one service uses a single database.

Change

Use serviceCredentials.User instead — the schema named after the service user, which the service actually owns.

Notes

• For non-shared databases name and user typically match, so behaviour is unchanged there.
• Existing extensions already created in the wrong schema are not moved by this change.

---

Note

Medium Risk
Changes where new extensions are created on shared databases; existing mis-placed extensions are not migrated, so behaviour only affects new installs.

Overview
installExtensions now runs CREATE EXTENSION ... WITH SCHEMA using serviceCredentials.User instead of serviceCredentials.Name, so extensions land in the schema owned by the service user.

On shared databases, the database name can match another service’s schema, which previously caused extensions to be created in the wrong schema. Dedicated databases where name and user match are unchanged.

This does not relocate extensions already created in the wrong schema.

^{Reviewed by Cursor Bugbot for commit 85ee40a. Configure here.}